home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Cream of the Crop 25
/
Cream of the Crop 25.iso
/
bbs
/
fe146.zip
/
FASTECHO.DOC
< prev
next >
Wrap
Text File
|
1997-04-01
|
645KB
|
11,602 lines
┌────────────────────────────────────────────────────────────────────┐
│ ░▓▓▓▓▓▓▓ ░▓ ░▓▓▓▓▓▓▓ ░▓ │
│ ░▓ ░▓ ░▓ ░▓ V1.46 │
│ ░▓ ░▓ ░▓ ░▓ │
│ ░▓▓▓▓▓ ░▓▓▓▓▓ ░▓▓▓▓▓ ░▓▓▓ ░▓▓▓▓▓ ░▓▓▓▓▓ ░▓▓▓▓▓▓ ░▓▓▓▓▓ │
│ ░▓ ▓▓ ░▓ ░▓ ░▓ ░▓ ░▓ ▓▓ ░▓ ▓▓ │
│ ░▓ ░▓▓▓▓▓ ░▓▓▓▓▓ ░▓ ░▓ ░▓ ░▓ ▓▓ ░▓ ▓▓ │
│ ░▓ ░▓ ▓▓ ▓▓ ░▓ ░▓ ░▓ ░▓ ▓▓ ░▓ ▓▓ │
│ ░▓ ░▓▓▓▓▓ ░▓▓▓▓▓ ░▓▓▓ ░▓▓▓▓▓ ░▓▓▓▓▓ ░▓ ▓▓ ░▓▓▓▓▓ │
└────────────────────────────────────────────────────────────────────┘
Copyright (C) 1991-1997 by Software Technik Burchhardt
written by Tobias Burchhardt
┌─────────────────────────────────────────────────┐
▄│ U S E R M A N U A L A N D T U T O R I A L │
█└─────────────────────────────────────────────────┘
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
┌─────────────────────────────┐
▄│ Written and copyright │
█│ by │
█│ Marco Piazza │
█│ Cesena, Italy, 30.03.1997 │
█└─────────────────────────────┘
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
FastEcho, FEUtil, FESetup and this documentation are protected
under the German and International copyright laws.
You are not authorized to copy, edit or modify these files
without written permission of the copyright holders.
For further license information check out LICENSE.DOC or
chapter (A) of this document.
For distribution license information refer to DISTRIB.DOC.
───────────────────────────────────────────────────────────────
FastEcho MANUAL - Table of contents -
───────────────────────────────────────────────────────────────────────
A) - Noncommercial Shareware Notice.......................1
B) - Foreword.............................................1
1 - What's FastEcho, what it does and when you need it...2
2 - Description..........................................3
3 - Minimal System Requirements..........................4
4 - Suggestions..........................................5
4.1 - Obtaining better performance.........................5
4.2 - Sharing the messagebase..............................5
4.3 - Optimized i386 routines..............................5
5 - T U T O R I A L......................................5
5.1 - Preliminary Operations...............................6
5.2 - The FESetup Main Menu................................6
5.3 - FESetup TopBar Dropdown menu.........................7
5.3.1 - FESetup, DOS command line switches...................8
5.4 - SYSTEM TopBar Dropdown menu.........................11
5.4.1 - Network addresses...................................11
5.4.2 - User names..........................................12
5.4.3 - Miscellaneous.......................................13
5.4.3.1 - Mailer..............................................13
5.4.3.2 - BBS Software........................................13
5.4.3.3 - Swapping............................................14
5.4.3.4 - Be 'quiet'..........................................14
5.4.4 - Pathnames...........................................15
5.4.4.1 - NetMail.............................................15
5.4.4.2 - Messagebase.........................................16
5.4.4.3 - Inbound.............................................16
5.4.4.4 - Unprotected Inbound.................................16
5.4.4.5 - Temporary Inbound...................................16
5.4.4.6 - Local Inbound.......................................17
5.4.4.7 - Outbound............................................17
5.4.4.8 - Temporary outbound..................................18
5.4.4.9 - Semaphores..........................................18
5.4.4.10 - BBS Configuration...................................19
5.4.4.11 - Static queue........................................19
5.4.4.12 - Swapping............................................19
5.4.4.13 - Rules (Directory definition)........................19
5.4.5 - Filenames...........................................20
5.4.5.1 - LogFile.............................................20
5.4.5.2 - AreaFix Log.........................................20
5.4.5.3 - Statistics..........................................21
5.4.6 - Parameters..........................................21
5.4.6.1 - Duperecords.........................................22
5.4.6.2 - Maximum open .QQQs..................................22
5.4.6.3 - Message buffer size.................................22
5.4.6.4 - Minimum Inbound .PKTs size..........................23
5.4.6.5 - Maximum Pkt size....................................23
5.4.6.6 - Maximum Messages per PKT............................23
5.4.6.7 - Maximum ARCmail size................................23
5.4.6.8 - Compress mail after.................................24
5.4.6.9 - Compress mail free..................................24
5.4.6.10 - Ignore old semaphores...............................24
5.4.7 - Advanced Options....................................24
5.4.7.1 - Keep tearline clean.................................25
5.4.7.2 - Retear..............................................25
5.4.7.3 - Tearline............................................26
5.4.7.4 - Auto Area Create....................................26
───────────────────────────────────────────────────────────────────────
FastEcho MANUAL - Table of contents -
───────────────────────────────────────────────────────────────────────
5.4.7.5 - Update Mailer Config................................26
5.4.7.6 - Update BBS config...................................26
5.4.7.7 - New area defaults...................................27
5.4.7.8 - Kill empty NetMails.................................27
5.4.7.9 - Kill duplicates.....................................28
5.4.7.10 - Share HMB...........................................28
5.4.7.11 - Force Mailer Rescan.................................28
5.4.7.12 - Respond to RRQ......................................29
5.4.7.13 - Use EMS for buffering...............................29
5.4.7.14 - Check .PKT destination..............................29
5.4.7.15 - Security............................................29
5.4.7.16 - Logging.............................................30
5.4.7.17 - Graphical tossing...................................30
5.4.7.18 - Toss Buffer.........................................30
5.4.7.19 - Temp. Outbound Type.................................31
5.4.8 - ARCmail Options.....................................31
5.4.8.1 - Archive extensions (Inbound)........................32
5.4.8.2 - Archive extensions (Outbound).......................32
5.4.8.3 - Mailer's semaphores (check).........................32
5.4.8.4 - Mailer's semaphores (create "In session")...........32
5.4.8.5 - Kill stray attaches.................................33
5.4.8.6 - Unpack Unprotected..................................33
5.4.8.7 - Check complete files................................33
5.4.8.8 - Max. compression ratio..............................33
5.4.9 - FEUtil parameters...................................34
5.4.9.1 - PURGE defaults......................................34
5.4.9.1.1 - PURGE - Messages....................................34
5.4.9.1.2 - PURGE - Days........................................35
5.4.9.1.3 - PURGE - Rcvd Days...................................35
5.4.9.2 - Use arrival date....................................35
5.4.9.3 - Autorenumber at.....................................35
5.4.9.4 - Exclude Users.......................................35
5.4.9.5 - Exclude SysOps......................................36
5.4.9.6 - Include USERS.BBS...................................36
5.4.9.7 - Keep NetMails.......................................36
5.4.9.8 - Kill grunged date...................................36
5.4.10 - Compression Programs................................37
5.4.10.1 - Rt. Values in compression programs..................38
5.4.11 - Decompression Programs..............................39
5.4.11.1 - Calling conventions.................................40
5.4.12 - External programs...................................40
5.4.12.1 - External programs (After Unpack)....................41
5.4.12.2 - External programs (Before Pack).....................41
5.4.13 - Group names.........................................41
5.4.14 - Origins.............................................42
5.4.14.1 - EchoMail vs. NetMail (matrix).......................42
5.4.14.1.1 - EchoMail............................................42
5.4.14.1.2 - NetMail.............................................43
5.5 - Data DropDown Menu..................................44
5.5.1 - Node Configuration..................................45
5.5.1.1 - Main Address........................................46
5.5.1.2 - ARCmail.............................................46
5.5.1.3 - Name................................................46
5.5.1.4 - Your AKA............................................46
5.5.1.5 - Passwords...........................................47
5.5.1.5.1 - Passwords (Packet)..................................47
5.5.1.5.2 - Passwords (AreaFix).................................47
───────────────────────────────────────────────────────────────────────
FastEcho MANUAL - Table of contents -
───────────────────────────────────────────────────────────────────────
5.5.1.6 - Status..............................................47
5.5.1.6.1 - Status (ARCmail)....................................47
5.5.1.6.2 - Status (AreaFix)....................................48
5.5.1.7 - Packer..............................................49
5.5.1.7.1 - Maximum size........................................49
5.5.1.8 - Groups..............................................50
5.5.1.9 - Security............................................50
5.5.1.10 - 4D/type 2+..........................................51
5.5.1.11 - TosScan.............................................51
5.5.1.12 - ARCmail 0.60........................................51
5.5.1.13 - Pack priority.......................................52
5.5.1.14 - Convert Umlaut......................................52
5.5.1.15 - Allow Area-Create...................................52
5.5.1.16 - New area default group..............................54
5.5.1.17 - Export by name......................................54
5.5.1.18 - AreaFix flags.......................................54
5.5.1.18.1 - Allow rescan........................................55
5.5.1.18.2 - Forward requests....................................55
5.5.1.18.3 - Send Rules..........................................55
5.5.1.18.4 - Allow %FROM.........................................55
5.5.1.18.5 - Allow area renaming.................................56
5.5.1.18.6 - Allow area deletion.................................56
5.5.1.18.7 - AreaFix type........................................56
5.5.1.18.8 - Remote program......................................56
5.5.1.18.9 - Add '+'.............................................57
5.5.1.18.10 - Add '---' <tearline>................................57
5.5.1.18.11 - Forward changes.....................................57
5.5.1.19 - Send Notify.........................................57
5.5.1.20 - Send Help...........................................58
5.5.1.21 - Passive.............................................58
5.5.1.22 - Automatic Passive...................................58
5.5.1.24 - 'Node Manager' Function Keys........................58
5.5.1.24.1 - Node Manager (Enter key)............................59
5.5.1.24.2 - Node Manager (F2-Routing)...........................59
5.5.1.24.3 - Node Manager (F3-Browse)............................60
5.5.1.24.4 - Node Manager (F4-Area List).........................61
5.5.1.24.5 - Node Manager (F5-Copy)..............................61
5.5.1.24.6 - Node Manager (Ins-New Entry)........................61
5.5.1.24.7 - Node Manager (Del-Delete)...........................62
5.5.2 - Group Area Defaults.................................62
5.5.2.1 - Comment (default)...................................63
5.5.2.2 - Origin (default)....................................63
5.5.2.3 - Type (default)......................................64
5.5.2.4 - Storage (default)...................................65
5.5.2.5 - Board (default).....................................65
5.5.2.6 - Path (default)......................................65
5.5.2.7 - Use Aka (default)...................................66
5.5.2.8 - Others "Group Area Defaults" switches...............66
5.5.2.9 - SEEN-BY (default)...................................66
5.5.2.10 - Export-To (default).................................67
5.5.3 - Area Configuration..................................68
5.5.3.1 - The Area definition layout..........................69
5.5.3.1.1 - Name................................................69
5.5.3.1.2 - Group...............................................70
5.5.3.1.3 - Comment.............................................70
5.5.3.1.4 - Origin..............................................71
5.5.3.1.5 - Type................................................71
───────────────────────────────────────────────────────────────────────
FastEcho MANUAL - Table of contents -
───────────────────────────────────────────────────────────────────────
5.5.3.1.6 - Storage.............................................72
5.5.3.1.7 - Board...............................................73
5.5.3.1.8 - Path................................................73
5.5.3.1.9 - Use Aka.............................................73
5.5.3.1.10 - Mandatory...........................................74
5.5.3.1.11 - Keep SEEN-BY........................................74
5.5.3.1.12 - Tiny SEEN-BY........................................74
5.5.3.1.13 - CPD Circular Path Detection.........................74
5.5.3.1.14 - Passive.............................................75
5.5.3.1.15 - Convert Umlaut......................................75
5.5.3.1.16 - Keep Users..........................................76
5.5.3.1.17 - Kill Read...........................................76
5.5.3.1.18 - Disable Passive.....................................76
5.5.3.1.19 - Remote changes......................................76
5.5.3.1.20 - Hide Area...........................................77
5.5.3.1.21 - Keep NetMails......................................77
5.5.3.1.22 - Purging.............................................77
5.5.3.1.22.1 - Purging (Msgs)......................................77
5.5.3.1.22.2 - Purging (Days)......................................77
5.5.3.1.22.3 - Purging (Rcvd Days).................................77
5.5.3.1.23 - Security............................................78
5.5.3.1.23.1 - Read (Security).....................................78
5.5.3.1.23.2 - Write (Security)....................................78
5.5.3.1.23.3 - Examples (Security).................................78
5.5.3.1.24 - SEEN-BY.............................................79
5.5.3.1.25 - Export-to...........................................79
5.5.3.1.26 - Active 'Area Manager' Function keys.................80
5.5.3.1.26.1 - Area Manager (Enter-Edit)...........................80
5.5.3.1.26.2 - Area Manager (F2-Sorting)...........................81
5.5.3.1.26.3 - Area Manager (F3-Tag)...............................81
5.5.3.1.26.3.1 - Tag by name.........................................81
5.5.3.1.26.3.2 - Tag by Group........................................82
5.5.3.1.26.4 - Area Manager (F4-Search)............................82
5.5.3.1.26.5 - Area Manager (F5-Copy)..............................82
5.5.3.1.26.6 - Area Manager (F6-Global)............................83
5.5.3.1.26.6.1 - Global (Add Node)...................................83
5.5.3.1.26.6.2 - Global (Delete Node)................................84
5.5.3.1.26.6.3 - Global (Replace <Node> with <Node>).................85
5.5.3.1.26.6.4 - Global (The other global items).....................85
5.5.3.1.26.7 - Area Manager (Ins/Del-Entry)........................85
5.5.4 - Carbon Copies.......................................86
5.5.4.1 - Test................................................86
5.5.4.2 - For string..........................................87
5.5.4.3 - Copy to.............................................87
5.5.4.4 - Examples............................................88
5.5.4.5 - Suggestions and notes...............................88
5.5.5 - What's AreaFix......................................89
5.5.5.1 - AreaFix MetaCommands................................89
5.5.5.1.1 - Linking one or more new areas.......................89
5.5.5.1.2 - Unlinking one or more areas.........................90
5.5.5.1.3 - Wilcarded Link/Unlink...............................90
5.5.5.1.5 - %QUERY..............................................91
5.5.5.1.6 - %INFO...............................................91
5.5.5.1.7 - %LIST...............................................91
5.5.5.1.8 - %UNLINKED...........................................91
5.5.5.1.9 - %AVAIL..............................................92
5.5.5.1.10 - %PAUSE..............................................92
───────────────────────────────────────────────────────────────────────
FastEcho MANUAL - Table of contents -
───────────────────────────────────────────────────────────────────────
5.5.5.1.11 - %RESUME.............................................92
5.5.5.1.12 - %NOTE...............................................92
5.5.5.1.13 - %RESCAN.............................................92
5.5.5.1.14 - %DAYS <nnn>.........................................93
5.5.5.1.15 - %MSGS <nnn>.........................................93
5.5.5.1.16 - %COMPRESS <Type> <?>................................94
5.5.5.1.17 - %PWD <password>.....................................94
5.5.5.1.18 - %PKTPWD <password>..................................95
5.5.5.1.19 - %FROM <net address>.................................95
5.5.5.1.20 - %HELP...............................................95
5.5.5.1.21 - %EXPORT.............................................96
5.5.5.1.22 - %NOEXPORT...........................................96
5.5.5.1.23 - %QUIT...............................................96
5.5.5.1.24 - Special %RESCAN syntax..............................96
5.5.5.1.25 - Special AreaFix MetaCommands........................96
5.5.6 - AreaFix Options.....................................97
5.5.6.1 - Allow %RESCAN.......................................98
5.5.6.2 - Rescan Defaults.....................................98
5.5.6.2.1 - Default for rescan..................................98
5.5.6.2.1.1 - Defaults for %MSGS..................................98
5.5.6.2.1.2 - Defaults for %DAYS..................................99
5.5.6.2.2 - Maximum for %DAYS...................................99
5.5.6.2.3 - Maximum for %MSGS...................................99
5.5.6.3 - Allow %PWD..........................................99
5.5.6.4 - Allow %PKTPWD.......................................99
5.5.6.5 - Allow %COMPRESS.....................................99
5.5.6.6 - Keep requests......................................100
5.5.6.7 - Keep receipts......................................100
5.5.6.8 - Scan before tossing................................100
5.5.6.9 - Detailed List......................................100
5.5.6.10 - Add list to receipts...............................100
5.5.6.11 - Password in %INFO..................................101
5.5.6.12 - Send conference rules..............................101
5.5.6.12.1 - Rulefile area tag prefix...........................101
5.5.6.13 - Max. receipt size..................................102
5.5.6.14 - AreaFix %HELP File.................................102
5.5.6.15 - Forward Requests...................................102
5.5.6.15.1 - Forward-to column..................................103
5.5.6.15.2 - List file..........................................103
5.5.6.15.2 - Remote program.....................................103
5.5.6.15.3 - Active column......................................103
5.5.6.15.4 - Setting up Forward AreaFix Requests................103
5.5.6.15.4.1 - Forward............................................104
5.5.6.15.4.2 - Unconditional......................................104
5.5.6.15.4.3 - Area List..........................................104
5.5.6.15.4.4 - List Type..........................................105
5.5.6.15.4.5 - Remote program.....................................105
5.5.6.15.4.6 - Deny list..........................................106
5.5.6.15.4.7 - Groups.............................................106
5.5.6.15.4.8 - Security...........................................107
5.5.6.15.4.9 - Add '+'............................................107
5.5.6.15.4.10 - Add '---'..........................................107
5.5.6.15.4.10 - New Area Default Group.............................107
5.5.6.15.4.11 - Create as passthrough..............................108
5.6 - Export DropDown Menu...............................109
5.6.1 - Export AREAS.BBS...................................109
5.6.2 - Export SQUISH.CFG..................................109
───────────────────────────────────────────────────────────────────────
FastEcho MANUAL - Table of contents -
───────────────────────────────────────────────────────────────────────
5.6.3 - Export Echolist....................................109
5.6.4 - Export ASCII file..................................109
5.6.5 - Export ROUTE.FE....................................110
5.7 - Import DropDown Menu...............................110
6 - USING FASTECHO.....................................111
6.1 - Help on line.......................................111
6.2 - FastEcho Toss......................................112
6.2.1 - FastEcho Toss -B...................................113
6.2.2 - FastEcho Toss -C...................................113
6.2.3 - FastEcho Toss -S...................................114
6.2.4 - FastEcho Toss -F...................................114
6.3 - FastEcho Scan......................................114
6.3.1 - FastEcho Scan -N...................................115
6.3.2 - FastEcho Scan -A...................................115
6.3.3 - FastEcho Scan -F...................................116
6.3.4 - FastEcho Scan -I...................................116
6.3.5 - FastEcho Scan -L<file>.............................116
6.4 - FastEcho Pack......................................117
6.4.1 - Routing (commandline) Statements...................117
6.4.1.1 - ShortCuts (wilcards/abbreviations/macros)..........117
6.4.1.1.1 - Shortened points routing...........................117
6.4.1.1.2 - Wildcarded addressing..............................118
6.4.1.1.3 - Direct Routing Examples............................118
6.4.2 - FastEcho Pack -R<route filename>...................119
6.4.2.1 - Routing (file) statements..........................119
6.4.2.1.1 - ROUTE-TO <target system> <addr> [<addr> <...>].....119
6.4.2.1.2 - NO-ROUTE <addr> [<addr> ...].......................120
6.4.2.1.3 - DIRECT <addr> [<addr> ...].........................120
6.4.2.1.4 - EXCEPT <addr> [<addr> ...].........................120
6.4.2.1.5 - FORWARD-TO <addr>..................................120
6.4.2.1.6 - FORWARD-FOR <addr>.................................121
6.4.2.2 - routing address' macro.............................121
6.4.2.2.1 - MYZONE.............................................121
6.4.2.2.2 - MYNET..............................................121
6.4.2.2.3 - MYPOINTS...........................................122
2.4.2.2.4 - LISTED.............................................122
6.4.2.3 - ROUTE.FE examples..................................122
6.4.3 - FastEcho Pack -I...................................123
6.4.4 - FastEcho Pack -F...................................123
6.4.5 - FastEcho Pack -P...................................123
6.5 - FastEcho Afix......................................124
6.6 - FastEcho Notify....................................124
6.6 - FastEcho Help......................................125
6.7 - FastEcho Relink....................................125
6.8 - FastEcho Stat......................................126
6.8.1 - FastEcho Stat -R...................................126
6.8.2 - FastEcho Stat -RS..................................126
6.8.3 - FastEcho Stat -S...................................126
6.8.4 - FastEcho Stat -G<groups>...........................126
6.8.5 - FastEcho Stat -H...................................127
6.8.6 - FastEcho Stat -N...................................127
6.8.7 - FastEcho Stat -O...................................127
7 - USING FEUtil.......................................127
7.1 - FEUtil Index.......................................128
7.2 - FEUtil Link........................................129
7.2.1 - FEUtil Link -F[orce]...............................130
7.2.2 - FEUtil Link -I[gnore]..............................130
───────────────────────────────────────────────────────────────────────
FastEcho MANUAL - Table of contents -
───────────────────────────────────────────────────────────────────────
7.3 - FEUtil Purge.......................................130
7.3.1 - FEUtil Purge -D[elete]............................131
7.4 - FEUtil Pack........................................131
7.4.1 - FEUtil Pack -F[orce]...............................131
7.4.2 - FEUtil Pack -O[verwrite]...........................132
7.4.3 - FEUtil Pack -R[enumber]............................132
7.4.4 - FEUtil Pack -D[elete]..............................132
7.4.5 - FEUtil Pack -Q[uick]...............................132
7.5 - FEUtil Sort........................................132
7.5.1 - FEUtil Sort -B[ackup]..............................133
7.6 - FEUtil Check.......................................133
7.6.1 - FEUtil Check -D[elete].............................133
7.7 - FEUtil Undelete....................................133
7.8 - FEUtil Move........................................134
7.9 - FEUtil Post........................................134
7.9.1 - <file> (mandatory).................................135
7.9.2 - <board> (mandatory)................................135
7.9.3 - [-Delete]..........................................135
7.9.4 - [-From name].......................................135
7.9.5 - [-To name].........................................135
7.9.6 - [-Subj text].......................................136
7.9.7 - [-Flags <flags>]...................................136
7.9.8 - [-Addr <address>]..................................136
7.9.9 - FEUtil Post Examples & Application.................136
7.10 - FEUtil Import......................................137
7.10.1 - FEUtil Import -Incl<file>..........................138
7.10.2 - FEUtil Import -Excl<file>..........................138
7.10.3 - FEUtil Import -FORCE...............................138
7.10.4 - Notes about FEUtil.................................139
8 - ENVIRONMENT VARIABLES..............................139
8.1 - FD, IM, DB Environment variables..................139
8.2 - FE environment variable............................140
8.3 - FEUTMP environment variable........................140
8.4 - HMBLOCK environment variable.......................140
8.5 - TZUTC environment variable.........................140
8.6 - FEMAXMEM environment variable......................141
8.7 - FEOPT environment variable.........................141
8.7.1 - USEBIOS flag.......................................141
8.7.2 - NO386 flag.........................................141
8.7.3 - NOEMS, NOXMS flags.................................142
8.7.4 - NOAFIX flag........................................142
8.7.5 - NOPACK flag........................................142
8.7.6 - NODUPES flag.......................................142
8.7.7 - NOEXPORT flag......................................142
8.7.8 - NOSEENBY flag......................................142
8.7.9 - NOMSGID flag.......................................143
8.7.10 - NOAUTOFAIL flag....................................143
8.7.11 - RDEBUG flag........................................143
8.7.12 - STRIPTEAR flag.....................................143
8.7.13 - PACKONE flag.......................................143
8.7.14 - SHOWCURSOR flag....................................143
8.7.15 - NOLIMIT flag.......................................143
8.7.16 - NORES flag.........................................144
8.7.17 - NOERREP flag.......................................144
8.7.18 - ZONEGATE flag......................................144
9 - Errorlevels........................................145
10 - Semaphore files....................................145
───────────────────────────────────────────────────────────────────────
FastEcho MANUAL - Table of contents -
───────────────────────────────────────────────────────────────────────
11 - Files created or used by FastEcho..................147
12 - Batch files example................................148
13 - Differences between DOS and 16 bit DPMI Versions...150
13.1 - DPMI Version Requirements..........................150
13.2 - Compatibility problems using the incl. DPMI server.150
13.3 - Precautions using the DPMI version.................150
13.4 - Differences between the DOS and Protected mode.....151
13.5 - DPMI Runtime module options........................151
Appendix (A) - Zone/Net/Node/Point................................152
Appendix (B) - Message kludges....................................153
Appendix (C) - Message Attributes.................................155
Appendix (D) - Technical notes....................................157
About the OS/2 and the DPMI version of FastEcho.....................159
FastEcho EchoMail & EchoFile Support................................163
Thanks..............................................................164
───────────────────────────────────────────────────────────────────────
FastEcho MANUAL - Preface -
───────────────────────────────────────────────────────────────────────
A) - Noncommercial Shareware Notice, Legal Stuff and Disclaimer
==========================================================
This is copyrighted software owned by Software Technik Burchhardt.
This is NOT public domain or freeware. Software Technik Burchhardt
grants you a TEMPORARY license to try this software for EVALUATION pur-
poses ONLY! You may use this package for an evaluation time of 30 days.
After this time you have to register FastEcho or stop using it ! Any
other or further use of this software is strictly forbidden and may re-
sult in legal action!
To register FastEcho, please refer to LICENSE.DOC and the order
forms included in REGISTER.RAR in this package. This is for NONCOMMER-
CIAL users only ! Commercial users please contact Software Technik
Burchhardt or an official FastEcho/commercial dealer.
FastEcho is provided 'as is', without warranty of any kind, neither
expressed nor implied. The author only guarantees that FastEcho and the
included tools occupy diskspace.
In no event will the author be liable to you for any damages, in-
cluding lost profits, lost savings or other incidental or consequential
damages arising out of the use of this program.
All mentioned products and packages are copyrighted by and trade-
marks of their respective holders.
Registered users receive a key file with a unique serial number.
These files are copyrighted stuff owned by Software Technik Burchhardt
and MUST NOT be distributed, hacked, reengineered etc. If you don't
follow these rules, your license expires immediately and legal actions
may be started against you.
One unique key allows you to run FastEcho on ONE computer at the
same time only (One computer runtime license). If you are using the sa-
me key on different systems (SysOp-Points for example) you need an ex-
tra license (key) for the other system(s)! This does not apply to mul-
tiine systems running FastEcho on the same machine but on several
lines.
B) - Foreword
========
Welcome to the Mail-Processing world. The program you're starting (or
you've been using for a long time), represents the state of art in the
world of electronic mail management. If you're a beginner I suggest you
to carefully follow the tutorial hereby included, keeping to the sug-
gested examples and directories; in this way you can quickly start your
work with FastEcho, so, after taking the right experience, you can fine
tune your configuration, changing the necessary parameters. Make sure
you understand every step in this tutorial before you decide to go
ahead. In case of difficulty, my best suggestion is, in fact, to revise
all previous steps. On the countrary, if you are an old-skilled Fast-
Echo User, you can use the same manual for consulting the new features
provided with this 1.46 release and how to use them relying upon the
"Smart-index". Have a nice journey!
───────────────────────────────────────────────────────────────────────
- 1 -
FastEcho MANUAL - Preface -
───────────────────────────────────────────────────────────────────────
1 - What's FastEcho, what it does and when you need it
==================================================
FastEcho is a complete electronic-mail-processor package and it can
perform a lot of operation (really a lot) but its MAIN targets are:
1) To export the messages you have entered locally (or which were ente-
red by a user of your BBS) from your preferred message base format
to your uplink and (if you have any) downlinks by means of proces-
sing it for a later distribution by your mailer.
2) To process the incoming mail bundles received by your mailer, store
the enclosed messages in your message base(s) and forward them to
your downlinks.
FastEcho, of course, does much more but these two operations, basic
in any electronic mail processing systems, are performed at a really
record speed. But now.. let's see at a glance, all the features given
back from FastEcho.
* Very fast and fully featured TOSSER/SCANNER for Hudson- (aka QBBS),
JAM-, Squish-, and Fido/*.MSG-Messagebase.
* 3 types of executables: normal DOS, extended DOS (DPMI, faster and
less memory problems) and OS/2 32 bit.
* powerful internal AreaFix with 'Forwarding'-feature and automatic un-
linking of passive Passthrough-areas (*registered version only*).
* Dupe checking database with up to 131000 (DOS), 262000 (DPMI) and
524000 (OS/2) entries
* Internal networking and multitasking support for several environments
* Complete NetMail routing and packing, easy handling of multiple
NetMail areas. Supports Binkley style static netmail packing.
* Nice Full-screen tossing mode
* Complete zone and point support. This applies to inbound as well as
outbound mail.
* Full ARCmail-security using passwords with 3 security levels and 2
different inbounds.
* Complete HMB-messagebase-maintenance-utility with JAM and Fido/*.MSG
support included.
* Full-screen integrated SETUP utility
* Easy to use area grouping with assigned defaults, use defaults for
each group in every new area (manually or automatically created).
* Automatic area-adding function with optional updating of your BBS
Configuration files (RA/QBBS/SBBS/ProBoard/TAG or Maximus).
───────────────────────────────────────────────────────────────────────
- 2 -
FastEcho MANUAL - Preface -
───────────────────────────────────────────────────────────────────────
* Carbon-Copy-function - filters out special messages and copies them
to special boards while tossing.
* Usage of available EMS and XMS memory for data and file-buffers
* Compatible with the FTSC standards FTS-0001 as well as FSC-0039 and
FSC-0048 and several others.
* Direct screen-writes, DESQview, PCMOS/386, Windows and OS/2 aware
Any of these features will be extensively explained later in this
manual.
2 - Description
===========
As told before, FastEcho is one of the fastest tosser/scanner for
the Hudson-Messagebase (formerly QBBS-Messagebase) currently available
and supports the JAM messagebase introduced with RemoteAccess 2.00 as
well as Squish (introduced with Maximus CBCS) and the old standard
*.MSG format. Further, the package contains all features needed to run
a point or a node; smart NetMail-packing/routing included. Typically
every step TOSS, SCAN and PACK is run in one pass, including un-/pa-
cking of mail-bundles, importing/exporting of mails and processing of
AreaFix-requests.
It can be run with FrontDoor, InterMail, D'Bridge, BinkleyTerm and
Portal of Power and has currently been tested with FrontDoor 2.12,
2.20, 2.30.beta, D'Bridge 1.5x, InterMail 2.2x, BinkleyTerm 2.5x,
Portal of Power 0.6x and McMail 1.0g. Of course it will run with any
other mailer compatible with one of the above.
A word of wisdom
================
Besides this manual you can find quick references to your questions
about the possibilities of FastEcho, simply by running all programs
with the "?" commandline switch, obtaining an usage-screen that will
help you in most cases. Using the "FESetup" Full Screen configuration
utility, you can further rely on the context-sensitive-online-Help
simply by pressing the F1 key.
───────────────────────────────────────────────────────────────────────
- 3 -
FastEcho MANUAL - Preface -
───────────────────────────────────────────────────────────────────────
3 - Minimal System Requirements
===========================
Hardware: * An IBM PC, XT, AT or compatible, optimized routines for
i386/i486/iPentium supported.
* the DPMI and the OS/2 executables need at least a i386
* At least 500kB of free conventional memory and 2MB
extended memory for the DPMI version
* Extended/Expanded memory suggested but not needed.
Software: * DOS 3.31+ or OS/2 2.x DOS compatibility box
* OS/2 2.x or 3.0 for the OS/2 executables
* FrontDoor 2.02 or 2.12/nc, FrontDoor 2.20/c, InterMail
2.29+, D'Bridge 1.53+, BinkleyTerm 2.50+ or Portal of Po-
wer 0.61+ and optionally RemoteAccess 1.11/2.00/2.50,
Maximus 2.02, QuickBBS 2.76+, SuperBBS 1.17+, ProBoard
2.00/2.02 or T.A.G. 2.6d+ or any other HMB/JAM/Squish or
*.MSG compatible BBS software
* A Fido/*.MSG style NetMail-directory
* A HMB style messagebase (even if you don't use it, you
have to define it and keep the empty files in the HMB
directory)
* At least one of these de-/compression utilities:
- PKZIP/PKUNZIP 1.10/2.04g
- ARJ 2.30/2.41a
- LHARC 1.13c/LHa 2.13
- PKPAK/PKUNPAK 3.61
- ARC 6.02
- ZOO 2.10
- PAK 2.51
- SQZ 1.08
- RAR 1.5x
- UC2 2.00
- Optionally an extractor program that copes with
different decompression programs like:
- General Unpack Shell GUS 1.90 or later
- PolyXarc 2.1a or later.
Environm.: * a FILES=??? in your CONFIG.SYS at least at the number of
systems specified in the Node-Manager plus 20
Example: 30 systems specified --> FILES=50
or: the value you define for 'Maximum open .QQQs' plus 20
───────────────────────────────────────────────────────────────────────
- 4 -
FastEcho MANUAL - Preface -
───────────────────────────────────────────────────────────────────────
4 - Suggestions
===========
4.1 - Obtaining better performance
For a much better performance on node systems forwarding mails to
downlinks it is strongly advised to set the 'Temporary Outbound' path
to a RAM disk with at least 1MB storage or to a local HardDisk when
working in a LAN environment. FastEcho will create outbound mail-
packets on this disk speeding up greatly the tossing. If you choose a
RAM disk, remember that, in order to obtain the maximum performances,
the more mail you have to forward, the bigger the RAM disk should be.
The RAM disk may be any size, FastEcho will automatically detect an
out-of-space condition and will act accordingly. You can further
increase performance by setting the 'Temporary Inbound' to a disk drive
different from the normal 'Outbound'. In this way FastEcho will extract
the ARCmail bundles to this drive and process them. This can reduce
disk accessing time (spent on head seeks) and especially in LAN
environments speed up tossing if the normal 'Inbound' was on a network
drive and the 'Temporary' is on a local drive.
4.2 - Sharing the messagebase
If SHARE is loaded, FastEcho supports messagebase sharing and Remo-
teAccess-messagebase-locking. You can read messages within one task
while tossing or scanning in the other task. This may also be called
'Network Mode'.
4.3 - Optimized i386 routines
FEUTIL and FastEcho automatically detect a i386 or higher CPU and
use some optimized routines. If you recognize any problems, you may use
"SET FEOPT=NO386" to disable the 386-support.
5 - T U T O R I A L
===============
Configuring FastEcho is easy, quick and simple indeed because you
can rely on the customized FESetup configuration utility; FESetup is
further equipped with a context-sensitive help-system that can, in most
cases, be useful while you're setting up your first installation or mo-
difying an already existent one. The help system gives you the choice
to immediately obtain information about the item you're working on,
simply by pressing the 'F1' key anywhere in FESetup. The following tu-
torial path, can be followed by beginners but should be normally con-
sulted too.
───────────────────────────────────────────────────────────────────────
- 5 -
FastEcho MANUAL - Tutorial - General -
───────────────────────────────────────────────────────────────────────
5.1 - Preliminary Operations
======================
Before starting with the FastEcho Installation you need some preli-
minary requirements. We are assuming that you still have a mailer
installed (such as FrontDoor or BinkleyTerm), so, you still know the
location of your NetMail, INBOUND and OUTBOUND directories as well. The
NetMail directory defined in your mailer will be called "Primary
Netmail Area" and will be usually shared between the mailer and
FastEcho. The INBOUND directory is the location where your mailer will
place the received mail bundles and the OUTBOUND directory is the
location where FastEcho will place the locally-prepared mail bundles,
ready to be sent to your uplink or ready to be picked up from your
downlinks. In this Tutorial we assume that you are ready to install
FastEcho on drive C: in a directory named "FAST". Copy the distribution
archive in the directory "FAST" and unarchive it with the suitable
unarchiver (in ARJ case you must use the following sintax: ARJ E
FE146.RAR). Naturally, you must have the ARJ.EXE archiver/unarchiver
available before doing it. After uncompressing the FE146.RAR archive,
you can immediately begin your new installation. From the DOS prompt
input:
C:\FAST>FESetup (and strike the "return" key)
5.2 - The FESetup Main Menu
=====================
Just a blink, and on you will be shown the following screen:
FESetup System Data Export Import F1 Help
░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░┌──────────────────────────────────────────────────────────────┐░░░
░░░│ Can't open C:\FAST\FastEcho.CFG: No such file or directory ! │░░░
░ C└──────────────────────────────────────────────────────────────┘ t░
░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
Press ESC to abort or Space to create new file...
Don't worry..It's not a problem! It only means that this one is
your first FastEcho installation and, so, FESetup isn't able to find
its configuration file "FastEcho.CFG" (as shown in the message). At
this point you can press the ESC key to give up and exit to DOS or,
better, press the "Space" Key to create an empty FastEcho.CFG file rea-
dy to be filled with your data. Assuming here that you press Space.
By pressing space, as said before, a fresh configuration file will
be created for you. If you aren't already registered, at this point you
will see the copyright screen too. Read these words carefully before
continuing with installation, it might be very important later.
───────────────────────────────────────────────────────────────────────
- 6 -
FastEcho MANUAL - Tutorial - General -
───────────────────────────────────────────────────────────────────────
FESetup System Data Export Import F1 Help
╔═════════════════════════ Shareware Notice ═════════════════════════╗
║ ║
║ This is copyrighted software owned by Software Technik Burchhardt. ║
║ This is NOT public domain nor free software. Software Technik ║
║ Burchhardt grants you a TEMPORARY license to try this software for ║
║ EVALUATION purposes ONLY ! You may use FastEcho for a 30 days ║
║ evaluation time. After this time you have to register FastEcho or ║
║ stop using it. Any other or further use of this software is ║
║ strictly forbidden and may result in legal action ! ║
║ ║
║ To register FastEcho in noncommercial environments, please refer ║
║ to LICENSE.DOC and the order forms included in REGISTER.RAR in ║
║ this package. ║
║ ║
║ Commercial users please contact Software Technik Burchhardt or an ║
║ official FastEcho/commercial dealer. ║
║ ║
║ Registration removes this delay and enables enhanced functions ! ║
║ ║
║ Press any key or wait for 15 seconds ... ║
║ ║
╚════════════════════════════════════════════════════════════════════╝
Press ESC to abort or Space to create new file...
When you finish reading the Shareware notice, you can press a key
to continue with FESetup.. The Shareware screen will disappear leaving
you free to work with FESetup. This screen is permanently removed once
you registered.
FESetup System Data Export Import F1 Help
░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
As you can see, the main FESetup screen has one topbar with five
items that represent the main topics of as many pull-down menues as you
can drop by means of both mouse or keyboard.
5.3 - FESetup TopBar DropDown menu
============================
In FESetup menu you can only do some general operations such as
obtain brief information about FastEcho, obtain a help screen about the
commandline switches available while calling FESetup, Shelling to DOS
and Quit the program.
FESetup System Data Export Import F1 Help
░░░┌──────────────┐░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░│>Information< │░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░│ Switches │░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░│ Shell to DOS │░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░│ Quit │░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░└──────────────┘░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
Shows general information about FESetup
───────────────────────────────────────────────────────────────────────
- 7 -
FastEcho MANUAL - Tutorial - FESetup pulldown menu -
───────────────────────────────────────────────────────────────────────
Note that the last row (at the bottom of the screen), always re-
ports a brief and quick explanation about the currently selected item.
Selecting the "Information" Item, will be shown a box containing a
little information about the current release you're using and the date
of compilation.
╔════════════ Information ═══════════╗
║ ║
║ FastEcho-Setup-Utility 1.46 ║
║ ║
║ Copyright (c) 1991-'97 by ║
║ Software Technik Burchhardt ║
║ ║
║ Compiled on xxx xx xxxx xx:xx:xx ║
║ ║
╚════════════════════════════════════╝
5.3.1 - FESetup, DOS command line switches
----------------------------------
The "Switches" item, instead, will display a box that summarize all
the commandline switches available calling FESetup from the DOS prompt.
╒══════════════════════════════════════════════════╡Usage╞═╕
│ │
│ You may call FESetup.EXE using following switches: │
│ │
│ -C Color display [with snow-checking on CGA] │
│ -A Use alternative colors │
│ -M Monochrome display │
│ -B access screen via Bios [very slow] │
│ │
│ -IE<file> Import Echolist <file> │
│ -O Overwrite existing descriptions [-IE only] │
│ │
│ -XA eXport AREAS.BBS file │
│ -X$ eXport SQUISH.CFG file │
│ -XE eXport ECHOLIST.FE file │
│ -G<groups> eXport only areas belonging to <groups> │
│ -XS eXport FECFG.TXT (ASCII configuration) │
│ │
│ -R<n>,<a> Resize your current configuration with a new │
│ maximum of <n> Node and <a> Area r │
│ │
╘══════════════════════════════════════════════════════════╛
This means that, from the DOS prompt, you can invoke FESetup
followed by one of these switches in order to obtain the described
result. I.E. : FESetup -C, FESetup -A etc.
FESetup -C
If you are using FastEcho with a system equipped with an old CGA
card, you could notice video noise while repainting/redrawing FESetup
screens. To avoid this boring problem, call FESetup with the -C com-
mandline switch from the DOS prompt.
───────────────────────────────────────────────────────────────────────
- 8 -
FastEcho MANUAL - Tutorial - FESetup pulldown menu -
───────────────────────────────────────────────────────────────────────
FESetup -A
Use this switch if you like the color-set FrontDoor-like.
FESetup -M
The -M switch force all FESetup screens in monochrome mode.
FESetup -B
By default, in FESetup, all video calls are done directly. If you
come across some problems with FESetup, when other software works con-
currently, or you need to do remote system mantainance via utilities
like "DoorWay" and it seems that you aren't able to display the
FESetup screen remotely, turn on FESetup with this switch. That may
solve your problems but note that, using the -B switch, FESetup will be
a lot slower than in the default direct-video-write mode.
FESetup -IE<File> [-O]
This switch is provided in order to simplify the operation of
import the EchoMail area description from a standard fidonet echo area
descriptions called Echolist (FIDONET.NA). You can do the same opera-
tion internally, by means of the "Import" DropDown-menu. If used in
conjunction with the -O switch, the already-existent description pre-
sents in FastEcho.cfg will be automatically overwritten. I.E. assuming
that you want automatic import in your FastEcho configuration the
description present in standard file FIDONET.NA overwriting all the
existing descriptions, you have to layout the following command:
FESetup -IEFIDONET.NA -O
Note that there isn't -any space- between the -IE switch and the file-
name FIDONET.NA (that's mandatory).
FESetup -XA
The -XA switch can be used to automatize the export of the standard
AREAS.BBS file containing your echo-tag followed by your
uplink/downlink addresses connected at each area.
FESetup -X$
Same as XA but, in this case, FESetup exports your settings for
Squish in a file called SQUISH.CFG
FESetup -XE
By using the -XE Switch FESetup exports the Echolist (Your confi-
gured areas each one with its comment) in a file called ECHOLIST.FE.
FESetup -G<Groups>
This switch is applicable to the XA, X$ and XE switch to make
possible FESetup exports only areas belonging to the groups specified
in <Groups>.
───────────────────────────────────────────────────────────────────────
- 9 -
FastEcho MANUAL - Tutorial - FESetup pulldown menu -
───────────────────────────────────────────────────────────────────────
FESetup -XS
The -XS switch can be used to automatically export a summary of
your current FastEcho configuration in one file which is "Human rea-
dable". Through this file you can check out the complete FastEcho con-
figuration at a glance. The default file name is FECFG.TXT.
FESetup -R<n>,<a>
This is the most important FESetup switch. It allows you to expand
or reduce the maximum number of available entries in area manager or in
node-manager that FastEcho can handle. In this way FastEcho can now (in
theory) support up to 1024 nodes and 3072 areas while the default set-
ting is 200 nodes and 1024 areas. Don't exaggerate with areas or nodes
because you may exaust all your conventional memory. Naturally this
switch could be useful also if you would like to reduce the default
areas and node value (if you don't need 200/1024) in order to leave
more conventional memory free. The correct syntax is as below.
If you need to increase the node entry fron 200 to 300 and the
areas from 1024 to 1500:
FESetup -R300,1500
If you need to decrease the node entry from 200 to 50 and the areas
from 1024 to 800
FESetup -R50,800
Note the absence of any spaces between the -R switch and the value
Be cautious:
While the DPMI and OS/2 executables won't have any problems working
with a high number of nodes and/or areas, the FastEcho DOS executable
and especially FESetup itself may have problems, therefore it might be
mandatory to have as many free conventional memory as possible.
Therefore after setting higher limits check if FESetup is still able to
load the configuration into memory, otherwise make use of the backup
file created in the previos run (FASTECHO.BAK) and copy it back to the
FASTECHO.CFG file.
───────────────────────────────────────────────────────────────────────
- 10 -
FastEcho MANUAL - Tutorial - System dropdown menu -
───────────────────────────────────────────────────────────────────────
5.4 - SYSTEM TopBar DropDown menu
===========================
Well, we're approaching the program core. Now, in order to go ahead
with our tutorial, we need to have one (or more) network addresses.
Cool!,you have one Fidonet and one ZyXELenet address and have decided
to keep the Fidonet one as main address and leave the ZyXELnet address
as AKA of your system. Your main address for this tutorial will be the
2:999/999 for Fidonet and 16:999/999 for ZyXELnet.
FESetup >System< Data Export Import F1 Help
░░░░░░░░░░░░░┌────────────────────────┐░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░│>Network addresses< │░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░│ User names │░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░│ Miscellaneous │░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░│ Pathnames │░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░│ Filenames │░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░│ Parameters │░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░│ Advanced Options │░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░│ ARCmail Options │░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░│ FEUTIL Parameters │░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░│ Compression Programs │Setup 1.46.xx ░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░│ Decompression Programs │░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
░░ Copyright │ External Programs │rchhardt. All rights reserved.░░
░░░░░░░░░░░░░│ Group names │░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░│ Origins │░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░└────────────────────────┘░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
This FESetup section needs to be filled with your data, addresses,
AKAs, pathnames, filenames and preferences before going farther; so,
place the highlight bar on the "Network addresses" item and hit the
return or enter key.
5.4.1 - Network addresses
-----------------
FastEcho, in order to work correctly, needs to be aware of all your
addresses, main and others known as AKAs (Also-Known-As). In this
outline you must insert your main address, akas and domain names. We
have before decided that, for this tutorial, you will assume two test
addresses; One main (2:999/999 for Fidonet) and one aka (16:999/999 for
ZyXELnet.ftn). Look at the screen reported below.
FESetup >System< Data Export Import F1 Help
░░░░░░░░░░░░░┌────────────────────────┐░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
░╔════════════════════════ Network addresses ════════════════════════╗░
░║ Main >2:999/999@fidonet< Aka 16 ║░
░║ Aka 1 16:999/999@ZyxelNet.ftn Aka 17 ║░
░║ Aka 2 Aka 18 ║░
░║ Aka 3 Aka 19 ║░
░║ Aka 4 Aka 20 ║░
░║ [...] [...] ║░
░║ Aka 15 Aka 31 ║░
░╚═══════════════════════════════════════════════════════════════════╝░
░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
Primary network address
───────────────────────────────────────────────────────────────────────
- 11 -
FastEcho MANUAL - Tutorial - System dropdown menu -
───────────────────────────────────────────────────────────────────────
Place the highlighted box over the Main item and press return. You
will see the further box that follows:
╔══════════════════ Main ══════════════════╗
║ Address: 2:999/999 ║
║ Domain name: fidonet ║
║ Point-Net: ║
╚══════════════════════════════════════════╝
In the "Address" item, you should write your main address
"2:999/999" and in the item that immediately follows type "fidonet"
which is the Domain name for the Fidonet address (we see about the
Point-Net item later). Strike now the "ESC" key and return to the "Net-
work addresses" main screen; now place the cursor upon "Aka 1" item and
press return; the same box seen before for the main address will ap-
pear. Now, What's your aka? 16:999/999, right! Write this in the "Ad-
dress" item and in the "Domain name" type:"ZyXELNet.ftn"; then press
the "return" and the "ESC" key to go back in the "Network adressess"
screen again. (Generally we can say that, in this layout, you must de-
clare your main address and all your akas. FastEcho supports a maximum
of 31 AKAs plus one Main address). When done, press F10 to save your
settings and return to System dropdown menu.
5.4.2 - User names
----------
In the user name definition, you can insert your name and the names
of all users that might access at FESetup and generally at your BBS or
point system. You could also define here other names for convenience
but these are only exceptions (and we'll see them later in the tips &
tricks section). FastEcho needs to know your name or your alias and the
name of all FastEcho users in order to reserve them a "special treat-
ment" when importing NetMail in the "secondary NetMail" area (be pa-
tient and you'll discover what this one is) or to preserve from dele-
tion "NetMail" or "EchoMail" addressed to them. Through this tutorial I
assume that your name is "Reed Richards"and your CoSysOp name is "Jonny
Storm". Now place the highlight box in "User name" item and press re-
turn. You'll se the following screen:
╔════════════════ Users ════════════════╗
║ Name ║
╟───────────────────────────────────────╢
║ 1 Reed Richards ║
║ 2 Jonny Storm ║
║ 3 ║
║ 4 ║
║ 5 ║
[...] [...]
║ 8 ║
║ 9 ║
║ 10 ║
║ 11 ║
╚═══════════════════════════════════════╝
Simply, under the "Name" column, write your first and second name
and the names of all the other FastEcho users. Then press F10 to save
your entry and to return to the main FESetup screen.
───────────────────────────────────────────────────────────────────────
- 12 -
FastEcho MANUAL - Tutorial - System dropdown menu -
───────────────────────────────────────────────────────────────────────
5.4.3 - Miscellaneous
-------------
In the Miscellaneous section, FastEcho expects your preference
about four items. It wants to know what mailer and what BBS system you
are using, what swapping technique you want to use and if you want the
external program called from FastEcho to output their data. Look at the
screen below:
FESetup System Data Export Import F1 Help
░░░░░░░░░░░░░┌────────────────────────┐░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░│ Network addresses │░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░│┌───────── Miscellaneous ─────────┐░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░││ Mailer FrontDoor │░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░││ BBS Software RemoteAccess 2.00 │░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░││ Swapping XMS/EMS │░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░││ Be 'quiet' None │░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░│└─────────────────────────────────┘░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░│ ARCmail Options │░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░│ [...] │░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░└────────────────────────┘░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
Highlighting the proper item by means of the arrows key, you have
the possibility to toggle along several choices simply by pressing the
"return" key.
5.4.3.1 - Mailer
FastEcho needs to know what mailer you're using in order to set the
proper method to handle the Inbound/outbound mail bundles. In the mai-
ler item you can select the following mailers: FrontDoor, Intermail,
D'bridge, Binkley/Xenia, Portal of Power and McMail. In this tutorial
we assume FrontDoor as mailer, so, strike return until "FrontDoor"
appears in the "mailer" field. Later, you will select the one you're
using.
5.4.3.2 - BBS Software
To obtain that FastEcho directly handles your BBS message areas,
you need to inform it about what BBS program you're currently running.
When the right BBS software will be specified in the "BBS Software"
item, FastEcho will be capable (only if you want) to add and update
your BBS EchoMail areas when it's necessary (I.E. when your uplink
starts to send you a new EchoMail area). In this tutorial we assume
"RemoteAccess 2.00" as default BBS Software but make sure to toggle the
correct BBS your are running. FastEcho currently can support the
Following BBS Software: Remote Access 1.11/2.00 and 2.50, QuickBBS
2.76, SuperBBS 1.17, ProBoard 2.00 and 2.02, T.A.G. 2.6 and Maximus
2.02
───────────────────────────────────────────────────────────────────────
- 13 -
FastEcho MANUAL - Tutorial - System dropdown menu -
───────────────────────────────────────────────────────────────────────
5.4.3.3 - Swapping
The "Swap" operation, generally, represents the most efficient way
to leave free as much conventional memory as possible when a "child"
program (which mostly can be an external program, such as packer or
other kind of utility) is called from the main program (FastEcho in our
case). This operation can be done, when possible, by discharging the
major part of the FastEcho executable code in a memory different from
the conventional leaving, in the precious main memory, only a couple of
bytes. This alternative discharging-memory could be the extended, the
expanded or, at least, the hard-disk memory. So, in this item, you can
choose what will be your preferred transitory-memory. Here you can tog-
gle through four options: XMS, EMS, XMS/EMS, Disk. With The XMS setting
FastEcho will try to swap in the extended memory only and, in case of
failure, it will swap to disk; with the EMS setting it will try to swap
in the expanded memory only and, if in case of failure, it will swap to
disk, with the XMS/EMS setting FastEcho will try to swap in the XMS be-
fore and, if this operation fails because it results exausted or
because other kinds of errors, it will try to swap in the Extended
memory, at last, if both operations fail, FastEcho will swap to disk as
usual; The Disk setting will fix the swapping operation directly to
disk without trying in XMS nor EMS memories. For this tutorial we'll
set this option to XMS/EMS.
5.4.3.4 - Be 'quiet'
The "Be 'quiet'" item allows you to decide if FastEcho has to
inhibit any message generated from external-called programs. They are
considered "external" all programs such as "Packer", "Unpacker" and
merely "External" programs defined through the proper option called
"external programs" that will be explained later in this manual. You
can select the appropriate "Be quiet" function through seven different
choices: "Pack", "Unpack", "Pack/Unpack", "External", "Pack/External",
"Unpack/External", "Pack/Unpack/External". Their names are self-ex-
plainatory. I.E.: the "Pack" item will inhibit only the messages of the
packer program when it will be called to pack your outbound mail, the
same for "Unpack"; the "External" item will try to inhibit the messages
generated from any optional program or utility that you've defined in
the "External-Programs" options (Such as PKTsorter, InBink, Bnp, and so
on). Note that the "be quiet" function works only if the external pro-
gram writes its messages "via BIOS calls". If, instead, the external
program displays its messages via "direct video calls", FastEcho won't
be able to intercept and suppress them. For this tutorial we'll set
this option to "None". When you have finished setting up the miscella-
neous section, press the ESC key to return to the System DropDown menu.
Your options will be automatically saved.
───────────────────────────────────────────────────────────────────────
- 14 -
FastEcho MANUAL - Tutorial - System dropdown menu -
───────────────────────────────────────────────────────────────────────
5.4.4 - Pathnames
---------
Inside the "PathNames" section you ought to inform FastEcho about
the positions of your working directories. As said before, in this tu-
torial we assume that you already have a mailer (FrontDoor) installed
on your system. No problem if you haven't exactly got this one because
the use of directories is the same. Well, place the higlighted box upon
the "Pathnames" item and strike the "Return" key. You'll see the
following layout on your screen:
FESetup System Data Export Import F1 Help
░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
░╔══════════════════════════════ Pathnames ══════════════════════════╗░
░║ NetMail: C:\FD\NetMail ║░
░║ Messagebase: C:\MESS ║░
░║ Inbound: C:\FD\INBOUND ║░
░║ Unprot.Inbound: C:\FD\INBOUND\UNPROT ║░
░║ Temp.Inbound: D:\TEMP ║░
░║ Local Inbound: C:\FAST\LOCINB ║░
░║ Outbound: C:\FD\OUTBOUND ║░
░║ Temp.Outbound: D:\TEMPOUT ║░
░║ Semaphores: C:\FD ║░
░║ BBS Config: C:\RA ║░
░║ Static queue: ║░
░║ Swapping: C:\TEMP ║░
░║ Rules: C:\FAST\RULES ║░
░╚═══════════════════════════════════════════════════════════════════╝░
░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
Now, let's see each of these items one by one.
5.4.4.1 - NetMail
In this field you must finger the location of the same NetMail di-
rectory you have previously defined setting up your mailer configura-
tion. The NetMail directory defined here is called "Primary NetMail
Area" that's always shared between the mail processor and the mailer.
On the countrary, a "Secondary NetMail Area", (that we'll define later
in the area configuration section) could be one NetMail area defined
internally in your messagebase (you might define one secondary netmail
area in HMB, JAM or *.MSG indifferently). We'll deal with the "Seconda-
ry NetMail Area" later in this manual; By now, remember that in this
field must define the pathname of your NetMail directory that you have
in common with your mailer. For this tutorial the "primary NetMail
directory path" will be "C:\FD\NetMail". When you have finished strike
"Return" to go to next field.
───────────────────────────────────────────────────────────────────────
- 15 -
FastEcho MANUAL - Tutorial - System dropdown menu -
───────────────────────────────────────────────────────────────────────
5.4.4.2 - Messagebase
You MUST here define the complete path and directory where you want
the Hudson Message Base structure to reside. If the HMB (or QBBS)
messagebase structure doesn't already exist, it will be automatically
created directly by FESetup. Well, you can choose to work with
messagebases such as JAM or SQUISH or *.MSG only or the same combined
of course but, in any cases you MUST have at least the HMB structure in
your choosen directory even if unused. (Don't worry, the HMB structures
takes only an handful of bytes)
5.4.4.3 - Inbound
The "Inbound" is the directory where your mailer (FrontDoor in this
tutorial) stores all the compressed mail bundles ready to be treated by
the mail processor. FastEcho, naturally, as mail processor, needs to
know where the aforesaid mail bundles are stored in order to find and
quickly process them. Both, in the mail processor and in the mailer,
you must define the "Inbound" directory and in both programs this
directory needs to be the same. If you are using FrontDoor as mailer,
then in this item may be defined the same directory you set in FDSetup
for the "Secure Inbound" item.
5.4.4.4 - Unprotected Inbound
Normally, a mailer can store the ARCmail packets received during
"Password Protected Mailer Sessions" and the ARCmail packets received
during "Unprotected Mailer Sessions" in different directories. During
"Protected Mailer Sessions" you receive ARCmail packets from known
system you have arranged a common password with and so you can well-
assume that the received file is somewhat secure, while, during
"Unprotected Mailer Sessions" you may receive ARCmail packets from
unknown systems that may, potentially, contain a mailbomb. FastEcho
gives you the choice to handle these potentially dangerous ARCmail
packets belonging from unknown systems allowing you to specify the
directory where your mailer stores the files received during
"Unprotected Mailer Session". If you then enable FastEcho to handle
these files (by means of the specific option you can find in "ARCmail
Option" see the paragraph 5.4.8.6) it will try to unpack these
unprotected ARCmail packets. But in any case only .PKTs containing
NetMail messages will be processed! This limitation can, in most cases,
grant the maximum security. If you followed the tutorial until now,
then leave this field empty.
5.4.4.5 - Temporary Inbound
As you certainly know, the mail bundles received by your mailer,
contains messages archived by means of utilities like ARC, PKZIP, ARJ
and so on. FastEcho needs to unarchive them to let itself process far-
ther the contained messages. These messages are called "PKTs" because
of their extension and, by default, are unarchived in the "Inbound"
directory. FastEcho has the power to unarchive the mail bundles, ex-
tracting the contained "PKTs" to another disk drive (this can be done
in order to increase the overall performances by reducing the disk seek
operation). If, upon your system, you have the availability of a second
───────────────────────────────────────────────────────────────────────
- 16 -
FastEcho MANUAL - Tutorial - System dropdown menu -
───────────────────────────────────────────────────────────────────────
disk drive, your better choice would be to point the temporary Inbound
to it or, again, if you're working in a LAN environment, it may be a
good idea to sight the "Temporary Inbound" to your local disk drive (if
available). It's strongly advised to avoid setting, as "Temporary In-
bound" one "RamDisk" because, incidental lack of main power, will risk
the loss of your daily mail. For this tutorial, if you have a second
hard disk installed, set the "Temporary Inbound" to it writing D:\TEMP.
If you are working in LAN environment then set it to point at your
local HDD; If you haven't another hard disk drive nor local hard disk
drive, simply leave this field empty.
5.4.4.6 - Local Inbound
FastEcho, in the standard "inbound" directory, has the power to
check if the incoming PKTs have the correct authorization to be pro-
cessed, thanks to its standard security system carried out through the
use of PKT passwords and/or addresses checking; In the present "Local
Inbound" directory, instead, FastEcho doesn't perform any security che-
cking assuming that all pkts present inside the "local inbound"are al-
ready secure relying upon your personal supervision. In fact, the mail
packets (*.PKT), in the local inbound, must be moved manually or by
means of customized batch files or, moreover, could be automatically
created and placed therein by LOCAL programs such as TIC processors.
For our tutorial type in this field "C:\FAST\LOCIMB\" and press return.
5.4.4.7 - Outbound
This is the directory where FastEcho will place the prepared ARC-
mail bundles, containing your outgoing mail, ready to be sent to your
uplinks or picked up by yourdownlinks. In particular this directory
doesn't have to be defined in your mailer setup and is significant only
for FastEcho in order to inform where it has to store the outgoing ar-
chivied pkts. Then, how does the mailer (FrontDoor) finds these bundles
to send them? That's quite simple: FastEcho creates as many "file-at-
taches" as "ARCmail bundles" to be sent it generates in "Outbound" di-
rectory. Any "file-attach" message is addressed to the right remote
systems, in conformity to the proper destination of the ARCmail bun-
dles. The File-Attach is nothing particular, to tell the truth; it con-
sists only in a kind of empty NetMail message that FastEcho, of course,
will store in the "Primary NetMail" (See the above "NetMail" paragraph
for more information) which is commommly defined between FastEcho and
the Mailer (in fact, only through this method the Mailer can find the
outgoing mail). This empty NetMail message has one mandatory attribute
set :"File-Attach". What does the "File-Attach" attribute involve? It
means that this empty NetMail message, in its "subject" field, has a
reference (complete path and filename) pointing to the ARCmail bundle
to be sent. When a connection with a remote system, having some mail to
pick up, takes place, then your mailer can cope with this situation by
finding immediately, in the common defined "Primary NetMail",the
NetMail message addressed to the currently connected system in order to
send him it; now, if this NetMail message has got the "File Attach"
attribute set, the mailer will look in its "Subject" field finding the
complete pathname/filename of the ARCmail bundle (which is nothing more
than a normal file) to send to the remote system, performing the mail-
expedition. There are two main methods to handle the outbound mail: The
first is the Frontdoor/InterMail style method which is the aforesaid;
the second is the BinkleyTerm method that substantially differs a lot
───────────────────────────────────────────────────────────────────────
- 17 -
FastEcho MANUAL - Tutorial - System dropdown menu -
───────────────────────────────────────────────────────────────────────
from the one above described. In particular, the BinkleyTerm method
needs to write the outbound ARCmail bundles in different directories in
order to support the multi-zone capability, so, for example, if you're
using Binkley as Mailer, FastEcho will use the defined
"C:\FD\OUTBOUND" path to store the ARCmail bundles relative to the main
address only while, for the ARCmail bundles referred to your aka
(that's 16:999/999), FastEcho will create the custom directory
"C:FD\ZYXELNET". If you are using a Binkley compatible mailer which
does not support the domain outbound directories, set 'Mailer' to PoP
or McMail.
5.4.4.8 - Temporary outbound
This is another special FastEcho feature created in order to extra
increase the already high speed FastEcho performances. Thanks to this
option you can define the path where FastEcho will store the outbound
mail packets while it's engaged with other tasks such as scanning, tos-
sing or packing the messagebase. You can thus really increase the speed
by targetting this path to a ram-disk. You shall size the ram-disk ac-
cording to the quantity of mail you usually export, of course; I sug-
gest you keep the ram-disk size a bit larger than the maximum volume of
mail you usually export, but it is not necessary (and impossible on
high traffic systems such as HUBs). In a Local Area Network environment
it's advised to point this temporary outbound path to the local Hard
Disk. If you use this feature correctly, you will see your FastEcho
spring up like lightning. Later, this setting will need a subsequent
definition in "Advanced Options" but, no haste, we'll correctly ac-
comodate all the stuff gradually. By now, you can finger in this field
the correct path of your ramdisk (E:\TEMPOUT" for this tutorial) if you
haven't any ramdisk installed, or you don't need one, then simply leave
this field empty. (I suggest you aim this path to a subdirectory of
your ramdisk because, normally, the ram-disk root directory has a
really limited number of available entries).
5.4.4.9 - Semaphores
If you are working in a multiline environment you must input in
this field the correct path where you know that your mailer generates
its semaphore-files and where you want FastEcho to generate, when ne-
cessary, its semaphore-files as well. The semaphore files generated
from FastEcho will be fully understandable by your mailer according to
the 'Mailer' setting we have seen above in the "Miscellaneous" section.
But what's a semaphore file? A semaphore is only a zero-length file
created by a program which needs to inform another program that it can
or cannot perform some operations. These semaphores have specific stan-
dard names in conformity with the specific operations that they must
allow or deny. When the restrictive situation ceases then the semaphore
will be deleted consenting the other program (which is working concur-
rently) to operate unreservedly. There are other kinds of pseudo-sema-
phores that FastEcho can generate, such as the PACKHMB.FE or
NEWAREAS.FE files, called flag-files. These files will be generated
when particular situations take place (I.E. when your HMB messagebase
reaches its phisical limits) in order to inform your batch-file that is
is time to take the right remedy. In this field, input the system path-
name where your mailer is installed (C:\FD for this tutorial).
───────────────────────────────────────────────────────────────────────
- 18 -
FastEcho MANUAL - Tutorial - System dropdown menu -
───────────────────────────────────────────────────────────────────────
5.4.4.10 - BBS Configuration
If you are running a BBS system and you want FastEcho to directly per-
form some useful operations in your BBS EchoMail area manager directly,
without manual intervention, you ought to specify in this field the
path where the configuration file of your BBS system resides. FastEcho
will read and modify the BBS configuration file type, according to the
"BBS software" item we saw above in the "Miscellaneous" precinct. The
main operation that FastEcho can do directly on your BBS software
configuration is to update automatically the EchoMail areas when, for
example, your uplink starts to send one or more new areas without upon
your request (ot not); if you allow this particular operation FastEcho
will update automatically its configuration and, then, the BBS software
EchoMail configuration. (As said before, we are assuming RemoteAcces
2.00 as BBS software so input "C:\RA" as pathname in this field but, if
your BBS software resides in one different directory make sure to input
the right ones). This option is obviously useless for a Point-System.
5.4.4.11 - Static queue
This pathname will become only useful when you are running the
D'Bridge BBS software (If, before, in the "Miscellaneous" ->"Mailer"
item, you inserted a software different from D'Bridge then you'll find
this current item directly disabled and inaccessible and useless to
you). This is the path to your D'Bridge(tm) queue directory where
D'Bridge stores its outbound queue. When running on a D'Bridge system,
FastEcho can create and insert outgoing mail-bundles according to the
DB Xmail specifications, instead of creating *.MSG-style file-attach
messages created for FrontDoor(tm) systems. In following cases FastEcho
will create a *.MSG file-attach though:
* one of the base36 numbers is greater than 46655
* a point is not a point of your main address
5.4.4.12 - Swapping
In this field you might input the pathname of your preferred direc-
tory where you want FESetup and FastEcho to place their overlay-files
whenever a swap-operation is requested and you have previously enabled
the Swap-to-disk option directly or when you have selected the XMS/EMS
swapping technique but FastEcho detects that there isn't enough memory
to perform the swap.
5.4.4.13 - Rules
FastEcho AreaFix is capable to automatically send to your downlinks
the conference rules (area policies) of every new echomail area they
want to be linked via an AreaFix request. In this field you must define
the path pointing to the directory where are stored the conference rule
files for all the echomail areas you forward. See also paragraphs
5.5.1.18.3, 5.5.6.12 and 5.5.6.12.1.
.-.-.
Here you have finished tigh up your pathnames. Now press F10 to
return to the System-DropDown menu again.
───────────────────────────────────────────────────────────────────────
- 19 -
FastEcho MANUAL - Tutorial - System dropdown menu -
───────────────────────────────────────────────────────────────────────
5.4.5 - Filenames
---------
Highlight the Filenames item and press the return key; the follo-
wing box will appear:
FESetup System Data Export Import F1 Help
░░░░░░░░░░┌────────────────────────┐░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░│ Network addresses │░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░│ User names │░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░│ Miscellaneous │░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░│ Pathnames │░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░│ Filenames │░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░│ Parameters │░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
░╔═══════════════════════════ Filenames ═══════════════════════════╗░
░║ Logfile: C:\FAST\FAST.LOG ║░
░║ AreaFix Log: C:\FAST\AFIX.LOG ║░
░║ Statistics: C:\FAST\FAST.STA ║░
░╚═════════════════════════════════════════════════════════════════╝░
░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
Press F10 to save or ESC to abort editing...
FastEcho has the ability to create two helpful files called log-
files and one report-file for the EchoMail-traffic statistics. Here you
can define the names of these files and the location where you want
FastEcho to store them. If you leave these field empty the log and
statistic files won't be created at all. It's recommended to insert
here the complete path and filenames of the log files.
5.4.5.1 - LogFile
The main logfile represents the "storyboard" of what FastEcho does.
All the operations that FastEcho performs can be zealously reported in
this file. The quantity of information that FastEcho can report in, de-
pends on the farther setting that we'll see later in the "Advanced Op-
tion" section. If you don't want any logfile, simply leave this field
empty, but It's unprofitable and I strongly discourage you to do it.
For this tutorial type: "C:\FAST\FAST.LOG" and FastEcho will immediate-
ly be qualified to create it.
5.4.5.2 - AreaFix Log
It's a separate log file that reports only the AreaFix operations
performed by FastEcho. In it will be kept the report of any single ac-
tion of the AreaFix Manager which is invoked with the command:
FastEcho Afix
In order to qualify FastEcho to create this log, you must type in
this field the path and name of the file you want for it. Leaving it
blank, the AreaFix log will be disabled but it's certainly not a sugge-
sted choice. For questions or further information about how to use the
AreaFix manager, look in the "AreaFix" Chapter. For this tutorial input
"C:\FAST\AFIX.LOG" in the AreaFix Log field. You can not specify the
same file name for both the normal log file and the AreaFix log.
───────────────────────────────────────────────────────────────────────
- 20 -
FastEcho MANUAL - Tutorial - System dropdown menu -
───────────────────────────────────────────────────────────────────────
5.4.5.3 - Statistics
Having the choice to generate statistics about the quantity and the
ratio of received/sent mail, tidily subdivided by provenance groups or
arranged in accordance with the node that sends or picks up it, may be
very useful for you. Simply putting in this field the path and the name
of your desired ASCII statistic files, you will qualify FastEcho to ge-
nerate the statistics through the use of the command:
FastEcho stat
If you have followed the tutorial until now, then type in the "Sta-
tistic" field "C:\FAST\FAST.STA"
.-.-.
Here you have finished the filenames dressing. Press F10 to save
your entry and return to the System DropDown Menu.
5.4.6 - Parameters
----------
In the "Parameters" section you must setup several options regard-
ing minor parameters. Starting this section is simple, move the high-
lighted box upon the "Parameters" item and press the return key. You'll
see the "Parameters" Box appear on your screen. Note that at the bottom
of your screen a brief explanation referenced to the currently
highlighted item is always present.
FESetup System Data Export Import F1 Help
░░░░░░░░░░┌────────────────────────┐░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░│ Network addresses │░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░│ User names │░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░│ Miscellaneous │░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░│ Pathnames │░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░│┌──────── Parameters ────────┐░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░││>Duperecords< 5000 │░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░││ Maximum open .QQQs 0 │░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░││ Message buffer size 0 │░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░││ Minimum inbound .PKTs 0 │░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░││ Maximum .PKT size 200 │░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░││ Max. # Msgs per .PKT 0 │.xx ░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░││ Maximum ARCmail size 0 │░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░││ Compress mail after 0 │░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░░ Copyr││ Compress mail free 0 │dt. All rights reserved. ░░░░░
░░░░░░░░░░││ Ignore old semaphores 0 │░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░│└────────────────────────────┘░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░│ Origins │░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░└────────────────────────┘░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
Number of duperecords to be kept in database; 0 = no dupe-checking
───────────────────────────────────────────────────────────────────────
- 21 -
FastEcho MANUAL - Tutorial - System dropdown menu -
───────────────────────────────────────────────────────────────────────
5.4.6.1 - Duperecords
FastEcho can keep track of your already processed messages in one
of its own particular databases; that's because, doing so, it can imme-
diately detect and refuse any already processed message that may be
present in your daily mail as duplicate. It isn't infrequently, in
fact, that your connected system could generate dupe messages caused by
its misconfigured systems or other errors; well, FastEcho can handle
this potential problem simply qualifing this option. In the Duperecords
field type the number representing the maximum size you wish for the
FastEcho-Duperecord-Database. Each record in the dupe databases
represents an already processed message, so, we can say that the number
x you'll insert here will consist in the last x processed messages.
It's useless, at this point, to remember that the bigger this number
will be, the more accurate dupecheck you will obtain. All dupes
detected thanks to this function can be directly deleted or copied and
saved in a custom "DupeBoard" area for further processing. Leaving in
this field the 0 value will disable the Dupechecking function. Your
choices can range from 1000 to 131000 (for the DOS executable, 262000
for the DPMI version and 524000 for the OS/2 version). If you have fol-
lowed the tutorial until now, then type in, at least, the value 5000
for the duperecord field.
5.4.6.2 - Maximum open .QQQs
The *.QQQ files are files containing outgoing messages that you
have locally created or that you are forwarding to other systems. These
*.QQQ files, of course, are not still ready to be sent because their
intermediate status, in fact FastEcho will rename them to *.PKT soon
and, further, they will be archived in a mail bundle ready to be sent.
In order to speed up the overall performances, FastEcho can keep
several .QQQ open simultaneously. The more open *.QQQs you will keep o-
pen via this option, the quicker FastEcho will result. Consider that
you cannot exaggerate with this number. The rule is that you can set as
many maximum open *.QQQs in this field, as many FILES=XX handles you
set in your config.sys file. If, in this field, you exceed the
Config.sys setting then FastEcho will stop with an error. Your possible
choices can range from 0 to 200. If you have followed the tutorial
until now, then leave the 0 value for this field. Only if you are per-
fectly aware of the FILES setting in you Config.sys type in this field
the correct value.
5.4.6.3 - Message buffer size
While FastEcho performs the toss or scan operations, it avails it-
self of a buffer containing one message at time. The present item is
needed to define the maximum size in kilobytes of this buffer and,thus,
the maximum size in kilobytes of a message that can be tossed or scan-
ned. the bigger this "message buffer size" will be, the bigger the size
of a single message could be. My only suggestion is to use a buffer as
large as possible, reducing it only in case you notice that your compu-
ter is short on memory. Using a large buffer doesn't affect the tossing
or scanning performances. In this case the admittible values range from
16kB to 64kB (upto 512kB may be setup for the OS/2 version). Only for
this tutorial, leave the message buffer size at 0 value (leaving 0 it
defaults to 32k) then, after you have completed the installation, go
back and tune this parameter.
───────────────────────────────────────────────────────────────────────
- 22 -
FastEcho MANUAL - Tutorial - System dropdown menu -
───────────────────────────────────────────────────────────────────────
5.4.6.4 - Minimum Inbound .PKTs (echomail)
This function can tune the size of each inbound echomail packet.
While FastEcho tosses your mail, and only after the mail bundles has
been unarchived, it computes the global size of your inbound mail pa-
ckets processing it only if the the calculated size is higher than the
values spcified in this option. When the total size of the inbound PKTs
results below the fixed limit then the PKts are left temporarily unpro-
cessed until, on a later call, is received mail enough to overtake it.
Note that this function only involves mail packets containing echomail.
The PKTs containing NetMail will be always processed instead.
5.4.6.5 - Maximum .PKT size
Through this option you can calibrate the maximum size of each
outbound mail packet. As said before, the mail packets (*.PKT) are fi-
les containing all the inbound or outbound messages in an intermediate
form: All the single messages are joined in this unarchived file. In
this case we are talking about the outbound mail packets that FastEcho
creates before archiving them. When a single mail packet becomes too
big, some system receiving it may have problems, thus, by means of this
option, you can fix, with some tolerance, the maximum size of an out-
bound PKT to the designed. The dimension,of course, cannot be exactly
the same you specified, because you can't force the messages stored in-
side the packets to have exact limits, so, the final size of the crea-
ted packets may sligtly vary from the one you defined within some tole-
rance. When using the "Maximum ARCmail size" feature you ought to well
select the size of packets in order to obtain pretty constant archive
sizes with variations of only some percent. For this tutorial leave
initially this value as (0).
5.4.6.6 - Maximum Messages per PKT
Via this function you will be able to fix the maximum message num-
ber that can be contained in a single mail packet. If this imposed
limit is be reached during the toss operation then a new packet will be
created, therefore, you will have as many packets as many times this
limit will be excedeed. For this tutorial put 200 in this field.
5.4.6.7 - Maximum ARCmail size
The value defined in this field has the task to fix the default
size in Kilobytes of the outbound ARCmail bundles which FastEcho will
generate for all the system configured in Node Manager. In other words,
this value becomes the effective one only for the nodes you haven't
previously settled by means of the more specific "Maximum size" option,
definable individually for every configured system (see the paragraph
5.5.1.7.1 in Node manager section). To fine tune this feature you must
also define the "average compression ratio", the "Maximum PKTs size and
the "Maximum size" items (read carefully the chapters 5.4.10, 5.4.6.4
and 5.5.1.7.1).
───────────────────────────────────────────────────────────────────────
- 23 -
FastEcho MANUAL - Tutorial - System dropdown menu -
───────────────────────────────────────────────────────────────────────
5.4.6.8 - Compress mail after
This function was introduced in FastEcho in order to solve the "low
on diskspace" potential problem that could arise if you usually process
large volumes of mail and forward it to a lotconnected systems. With
this feature enabled, when you toss your just received mail, FastEcho
keeps an eye on the quantity in bytes of the already processed mail and
when this quantity reaches the size you fixed in the actually treated
function, then FastEcho will suspend tossing, starting to pack,
instead, the mail packets created so far; when finished archiving the
new mail packets, FastEcho will resume the previously suspended toss
operation in order to process the remaining mail. I strongly suggest
you to enable the "Memory Swapping" feature (see 5.4.3.3 and 5.4.4.11
for further information) when using this option, otherwise you may
exaust all your conventional memory when packing the mail. For this
tutorial leave (0) in this field.
5.4.6.9 - Compress mail free
With this feature enabled you can establish when FastEcho has to
suspend the inbound toss operation in accordance with the free space
existing on your outbound drive. As you can see, this function is a lot
similar to the previous: "Compress mail after". The only difference is
only the object that's checked while all other operations on the mail
packets will be the same. For this tutorial leave (0) in this field.
5.4.6.10 - Ignore old semaphores
In order to work concurrently with other programs on multitasking
and/or multinines environments, FastEcho creates some semaphore files
(like FEBUSY). These semaphore files might, in some rare cases (power
line failure or system hang) erroneously stop FastEcho when it's no
needed. This behavior can be resolved thanks to this setting. Here you
can tell FastEcho to ignore all semaphore files if they are older than
X hours so, when it finds expired semaphores, deletes them resuming the
process as if the file wasn't found.
.-.-.
Here, finishes the Parameters setting. Now press the ESC key to re-
turn to the System DropDown Menu. Your entry will be automatically sa-
ved.
5.4.7 - Advanced Options
----------------
In the Advanced Options Box you can adjust perfectly, in accordance
with your needs, all switches which can improve the FastEcho capabili-
ties and, consequently its productivity. This can be done by way of se-
veral additions, some regarding add-on features, others to try and fur-
therly increase the FastEcho speed performances and the scanning/tos-
sing tolerance too. Let's see all of them. Place the highlighted box on
"Advanced Options" item and strike the return key. The following box
will be shown.
───────────────────────────────────────────────────────────────────────
- 24 -
FastEcho MANUAL - Tutorial - System dropdown menu -
───────────────────────────────────────────────────────────────────────
FESetup System Data Export Import F1 Help
░░░░░░░░░┌────────────────────────┐░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░│ Network addresses │░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░│┌───── Advanced Options ─────┐░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░││>Keep tearline clean< No │░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░││ Retear Yes │░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░││ └─Tearline │░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░││ Auto-Area-Create Yes │░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░││ └┬Update mailer config Yes │░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░││ └┬Update BBS config Yes │░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░││ └New area defaults │░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░││ Kill empty NetMails Yes │░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░││ Kill duplicates No │ 2.xx. ░░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░││ Share HMB No │░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░ Copyr││ Force Mailer rescan Yes │hardt. All rights reserved. ░░░
░░░░░░░░░││ Respond to RRQ No │░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░││ Use EMS for buffering Yes │░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░└│ Check .PKT destination No │░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░│ Security None │░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░│ Logging Full │░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░│ Graphical Tossing Full │░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░│ Toss Buffers Large │░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░│ Temp. Outb. Type RamDisk │░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░└────────────────────────────┘░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
Change tearlines of EchoMails when exporting
5.4.7.1 - Keep tearline clean
By enabling this option FastEcho will strip the text from tearlines
(that may be previously inserted by a message editor) it will be able
to find in any outgoing EchoMail message it processes during the
"FastEcho Scan" operation. This feature makes easier the "retearing" to
an empty tearline operation, you need, in the past, to perform the same
operation. For this tutorial leave this option enabled.
5.4.7.2 - Retear
The term "Retear" means to qualify FastEcho to strip any Tearline
that may be present in any EchoMail message generated by your system,
replacing it with your preferred one (you will be able to specify which
one in the following "Tearline" option). The tearlines are always auto-
matically placed by your message editor. But what's the tearline? Ori-
ginally, the tearline was only the means to communicate to mail proces-
sor where the text, that you usually type in a message, finishes.
Substantially one tearline consists in three visible consecutive dashes
(---) placed in a new line at the end of the message you typed and this
is the mandatory part that FastEcho, or other programs, will never
touch. But there is another tearline part which is optional: the part
that, separated by one single space, may immediately follow the three
aforesaid dashes. In the BBS world, recently, this optional part has
become erroneously too long and mostly decorative: that's wrong! The
meaning of the tearline must be the communication of useful and non-re-
petitive information, furthermore, its lenght must be kept within fixed
limits. So, if you decide to insert the optional part of the tearline,
then make sure to avoid useless, repetitive or foolish words therein,
───────────────────────────────────────────────────────────────────────
- 25 -
FastEcho MANUAL - Tutorial - System dropdown menu -
───────────────────────────────────────────────────────────────────────
further, make sure not to go beyond the 30 characters limit. This is a
feature reserved to registered user. If you aren't already registered
then you won't be able to access this option.
5.4.7.3 - Tearline
Placing the highlight pointer on the "Tearline" field and pressing
the return key, the following little box will be drawn on your screen:
╔═══════════ Tearline ════════════╗
║ Tearlines are a waste of space ║
╚═════════════════════════════════╝
Here, you can specify the optional part of the tearline that you
wish to see inserted in your messages. If the optional tearline message
is inserted or does not, it depends, of course, on the "Retear" switch
status. Read carefully the previous Item before you type something
herein.
5.4.7.4 - Auto Area Create
If your uplink starts to send you areas that are not yet in your
area database,normally, FastEcho will toss the messages contained in
the undefined areas in a particular area called "BadMail area" in order
to submit its contents to you; then if you decide to switch these areas
linked you will have to perform, manually, several operations such as,
check the tags of all the boards tossed in BadMail, define these areas
in the area manager of FastEcho, update the area manager of your mailer
and, last of all, the area manager of your BBS software; finally you
should retoss the BadMail in the newly created boards. It's really a
boring operation, isn't it? If you qualify the FastEcho "Auto Area
Create" feature, then automatically FastEcho will do all this stuff for
you and, as a matter of fact, it is very convenient. Although, by way
of "Auto Area Create" switches, you can generally enable FastEcho to
perform this feature, each your uplinks, separately, need to be able to
send you undefined areas too. For our tutorial you can set this item to
YES.
5.4.7.5 - Update Mailer Config
The present feature, and also the next two, are strictly connected
to the previous "Auto Area Create" item. This one, in particular, has
the task of selecting if you want, for FastEcho "Auto Area Create" to
update the Area-manager of your Mailer (In our case it will add the re-
lative folder, or folders, inside FrontDoor folder manager configura-
tion). For our tutorial put "Yes" in this item.
5.4.7.6 - Update BBS config
Likewise the previous, the functionality of this item is subor-
dinate to the "Auto Area Create" item status. While the "Update Mailer
Config" feature updates the Mailer "Areas" configuration, the present
does the same task but on the BBS "Areas" configuration.
Only if you're running a BBS, then switch on this item by toggling
it to "Yes".
───────────────────────────────────────────────────────────────────────
- 26 -
FastEcho MANUAL - Tutorial - System dropdown menu -
───────────────────────────────────────────────────────────────────────
5.4.7.7 - New area defaults
If you enabled the "Update BBS config" feature, then FastEcho will
try to add, in your BBS configuration, any new areas that your quali-
fied uplink starts to send you without your expressed request. Natu-
rally, FastEcho has to know in advance, what kind of BBS system you are
actually running, taking this information from previously selected
items located in "Miscellaneous" section (see paragraph 5.4.3.2) and,
of course, it needs to know the default value you want for the area
created automatically. Note that if you wish to let FastEcho add auto-
matically the new areas in your BBS configuration you ought to dress
the new area default too. So place the highlighted box on this item and
strike the return key; doing so, you will see the following mask:
FESetup System Data Export Import F1 Help
░░░░░░░░░┌────────────────────────┐░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░│ Network addresses │░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
░╔══════════════════════ MESSAGES.RA defaults ═══════════════════════╗░
░║ ║░
░║ Status Pvt/Pub ║░
░║ Users Real names only ║░
░║ ║░
░║ Echoinfo No Age 0 AltGroup1 0 ║░
░║ Combined No Group 0 AltGroup2 0 ║░
░║ Deletes No AltGroup3 0 ║░
░║ SoftCRs No AllGroups No ║░
░║ Origin ║░
░║ Address Main ║░
░║ ║░
░║ Read 0 Write 0 SysOp 0 ║░
░║ A flag -------- A flag -------- A flag -------- ║░
░║ B flag -------- B flag -------- B flag -------- ║░
░║ C flag -------- C flag -------- C flag -------- ║░
░║ D flag -------- D flag -------- D flag -------- ║░
░║ ║░
░╚═══════════════════════════════════════════════════════════════════╝░
░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
Private/public, private only, public only or read-only messages
In this mask you can define the default values for the BBS areas
which FastEcho will add automatically. You might observe that this lay-
out is exactly like the RemoteAcces area definition screen. In fact
FastEcho is aware of your BBS system by means of the setting you dispo-
sed in "Miscellaneous" section at "BBS system" item (see 5.4.3.2) so,
It smartly show the correct screen according. If you are unsure about
the means of each of these "MESSAGES.RA default" items, then refer to
your BBS software documentation.
5.4.7.8 - Kill empty NetMails
Toggling this option to "Yes" will qualify FastEcho to directly de-
lete all NetMails which haven't any significant text line in their bo-
dy. These empty NetMails are, usually, file attaches that, after having
solved their task of carrying the file as far as your system, they be-
come really useless to you. For our tutorial I can say that for both,
BBS or point system it is always suggested to switch this option acti-
ve.
───────────────────────────────────────────────────────────────────────
- 27 -
FastEcho MANUAL - Tutorial - System dropdown menu -
───────────────────────────────────────────────────────────────────────
5.4.7.9 - Kill duplicates
As we saw in paragraph 5.4.6.1, FastEcho has the capability of in-
tercepting all duplicate messages it tosses and immediately discards
and copies them into a particular mandatory area flagged "DupeMail"
(You will know more about the mandatory DupeMail area later in this
manual). These dupeplicates could be refused and copied in the
"DupeMail" areato allow you to revise and check them, or could be
refused and deleted directly. If, in this item, you toggle the "Yes"
status, the dupes will be deleted, with the "No" value, instead, they
will be kept, then, if you want, they could be manually deleted. For
our tutorial, switch this item to "No"
5.4.7.10 - Share HMB
This feature is only useful if you run your system in a multiline
or multitasking environment. In such environments, in fact, it could
happen that two or more programs try to write the same messagebase to-
gheter. This could cause severe problems in your messagebase if it hap-
pens without the adequate precautions. The very first of these pre-
cautions you must take is to load the DOS utility SHARE.EXE by way of
your AUTOEXEC.BAT when your system starts; the second is to switch on
this option in order to qualify FastEcho to use his record-locking pro-
cedure which is fully RemoteAccess compatible. Later, in this manual,
we shall see the functionality of the FastEcho companion environment
setting "HMBLOCK". For our tutorial I assume that you haven't a multi-
line or multitasking environment, so, toggle this option to "No" but,
if you are perfectly aware in what you are doing, then, make your choi-
ce here.
5.4.7.11 - Force Mailer Rescan
We talked before about Semaphores in the 5.4.4.8 paraghraph. Well,
if you enable this switch, toggling the "Yes" status, then you will
instruct FastEcho to create one particular Semaphore file that will
tell your mailer to perform an operation called "rescan". What is this
operation? As said before in several occasions, the primary-NetMail
directory, which is commonly defined between FastEcho and your mailer,
represents the board where every normal NetMail message and every file-
attach will transit. When FastEcho finishes exporting NetMail messages
from your secondary NetMail area or when it creates the ARCmail-
attaches in your primary NetMail area, then, the mailer must be aware
that, in the common NetMail area, there is mail to be processed. Your
mailer, when idle too, always waits for a particular semaphore capable
of waking it up and making it check in its work directory (the primary
NetMail area) if there is something to do. When it detects this
semaphore in the proper directory, it starts to search for new work in
the primary NetMail area. These semaphores have different names in
accordance with the mailer you are using. In our case the mailer is
FrontDoor so,these semaphores will be called FDRESCAN.NOW and
FMRESCAN.NOW. For D'Bridge, on the countrary, would be DBRIDGE.RSN
while for Binkleyterm it will be BTRESCAN.*. All the semaphores genera-
ted by FastEcho will be created in the directory you defined in the
"Semaphore" items. (See in PathNames section in paragraph 5.4.4.8.).
───────────────────────────────────────────────────────────────────────
- 28 -
FastEcho MANUAL - Tutorial - System dropdown menu -
───────────────────────────────────────────────────────────────────────
5.4.7.12 - Respond to RRQ
The RRQ is a message attribute that means (Return Receipt reQuest)
when a message has reached its destination and is processed by a mail
processor it will create a receipt message telling the sender that and
when the NetMail arrived. If you are a FastEcho registered user who
wishs to enable this useful feature then toggle it to on, otherwise it
doesn't matter, because you won't have any access to it.
5.4.7.13 - Use EMS for buffering
If you come across some EMS errors so that you need to disable the
usage of all the available expanded memory that otherwise FastEcho au-
tomatically uses while it creates the outbound mail packets, then, sim-
ply toggle this option to "No". For this tutorial, instead, toggle this
option to "Yes" and, if running FastEcho after completing the tutorial
you notice some EMS errors,then go back and change this option to "No".
5.4.7.14 - Check .PKT destination
When you receive a mail packet from your up/downlinks FastEcho has
the ability to check it for its destination (as we'll see in the
Security 5.4.7.14 chapter). With this switch you can define three dif-
ferent FastEcho behaviors: if you toggle it to "Yes" it will refuse any
mail packets that are not addressed to your main address or to one of
your akas defined in "Network Adresses" section (See 5.4.1 chapter);
with this switch toggled to "fwd" (forward) FastEcho checks if the des-
tination of incoming mail packets matches at least one system defined
in the "Node Manager" section (In the "Node Manager" you must define
all systems, node or point, connected to you but we'll meet this one
later) and, if so, FastEcho directly moves this packet from the "In-
bound" directory to "Outbound" without processing it;only after the
mail processed throug the normal toss operation will be ready, the mo-
ved packets will be archived together. If you toggle this option to
"No" status, then no checking will be performed and all mail packets
will be tossed in normal way. For the tutorial, leave this option to
"No" status.
5.4.7.15 - Security
FastEcho, independently from your mailer, has its own security sys-
tem, based substantially upon two parameters: the addresses of the
connected systems and the password that an ARCmail bundle may have (You
ought know that the session password has really nothing to do with the
ARCmail-level password: the first is the password that you may agree
with a remote system to allow your mailer be really sure of recognizing
it for what it appears to be, letting it go farther with mail exchange;
the second, object of our discussion, is the password embedded in your
ARCmail bundle ready to be processed). This switch could have three
possible values: "None", "Normal" and "Full". When it's toggled to
"None" all the security features will be disabled, so, all incoming
mail packets will always be processed and tossed without any inspec-
tion, when it's switched to "Normal then FastEcho will check the add-
ress proveneance of this (or these) mail packet(s). If their original
address matches an address you defined in the "Node Manager" (We shall
see later in "Node Manager" section) then the mail packets will be pro-
cessed, otherwise they will be discarded and left in Inbound directory
───────────────────────────────────────────────────────────────────────
- 29 -
FastEcho MANUAL - Tutorial - System dropdown menu -
───────────────────────────────────────────────────────────────────────
with the .SEC extension. The "Full" security option checks both the pa-
cket's address origin and the aforesasid "Packet-password" (you can de-
fine this password in the "Passwords (ARCmail) 5.4.1.5.1" if necessary;
we'll see later) in case one of both fails the inspection, then the
entire mail packet will be renamed to *.SEC and left in inbound direc-
tory. Now leave it in this with the "None" status.
Note: if set to 'None', it will also disable the security checks
done for EchoMail on per-area-basis. Which means, in that case FastEcho
will import all messages in any area not checking whether the sending
system is allowed to send a message in that area (determined by either
the Export-to field or the security levels).
5.4.7.16 - Logging
As said in the 5.4.5.1 section, FastEcho can keep trace of all its
activities in a file called LogFile. It can, of course, put therein all
what it does but, thanks to this option, you can graduate too the quan-
tity of information you wish. Here you can select three options:
"Norm", "Full" and "None". In "Full" mode FastEcho will report all its
operations, in "Norm" mode it will report the essential operations on-
ly, in the "None" mode the logging will be disabled. It's obvious that
the more information you will let FastEcho write in its logfile, the
bigger it will become, so, if you want to keep it as short as possible,
toggle in this option the "Norm" status. For this tutorial, instead,
the better choice will be the "Full" status because in case of doubt
about what FastEcho does, you can refer to this logfile for debugging
purposes, so, you will be able to adjust your FastEcho configuration.
5.4.7.17 - Graphical tossing
FastEcho, when tossing, has a nice screen-interface that allows you
to see its tossing progress and gives you several "on-the-fly" informa-
tions such as how many mail packets it has to process, how many messa-
ges and how many EchoMail and NetMails there are, benchmark information
and so on. The information that FastEcho displays can be tuned by way
of this switch. In "None" mode you will see only textual information on
your screen, In "Norm" mode, the info will be shown in a "Fast window",
finally, In "Full" mode FastEcho will display the tossing information
in a "Full Windowed" screen. For our tutorial switch this item to
"Full" graphical tossing mode.
5.4.7.18 - Toss Buffer
The "toss buffer" represents the transit memory that FastEcho will
use while it performs the toss operation on mail-packets. It's evident
that the bigger this buffer will be, the faster FastEcho will run. The
only exception to this rule is that: if you are using an intelligent
controller for your hard disk unit or a staged-write harddisk cache
program, then you may not find great differences independently from the
"Toss Buffer" size youhave selected here. In all other cases, larger
buffers increase the FastEcho performances. The size of the "Toss-
Buffer" is selectable in three different values: "Large"=84 Kilobytes,
"Medium"=50 Kilobytes, "Small"=25 Kilobytes. As a general rule you
should always select here the "Large" buffer, reducing it afterwards
only in case you notice that your conventional memory exausts.
Following this tutorial, you will toggle here the "Large buffer"
status.
───────────────────────────────────────────────────────────────────────
- 30 -
FastEcho MANUAL - Tutorial - System dropdown menu -
───────────────────────────────────────────────────────────────────────
5.4.7.19 - Temp. Outbound Type
As introduced in the 5.4.4.7 paragraph, talking about "Temporary
Outbound": we said that this is another feature to increase the overall
FastEcho speed and it could be both a RamDisk or HardDisk. In "Temp.
Outbound" item we have defined the path; here, instead, we must define
its type according to our previous path definition. If you have follo-
wed this tutorial until now, then toggle this item to RamDisk status.
The difference between both settings is that when operating on a
RAM disk, before starting to create the ARCmail FastEcho will move all
outbound .QQQs from the RAM disk to your outbound directory (for
security reasons) while when operating on a hard disk this is not
necessary and only wastes time.
.-.-.
Here you have finished the dressing of the "Advanced Option" menu. Now
strike the ESC key to return to "System DropDown menu" again.
5.4.8 - ARCmail Options
---------------
Here we are going into a special feature that could be useful for
particular security purposes. Highlight The ARCmail Options item and
press the return key once. You will see the following menu:
FESetup >System< Data Export Import F1 Help
░░░░░░░░░░░░┌────────────────────────┐░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░│┌────── ARCmail Options ─────┐░░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░││>Archive extensions< │░░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░││ ├─Inbound 0-9 │░░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░││ └─Outbound 0-9 │░░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░││ Mailer's semaphores │░░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░││ ├─Check Yes │░░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░││ └─Create "in session" No │ 1.46 ░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░││ Kill stray attaches Yes │░░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░││ Unpack unprotected Yes │░░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░ Copyrigh││ Check complete files Yes │t. All rights reserved. ░░░
░░░░░░░░░░░░││ Max. compression ratio 0 │░░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░│└────────────────────────────┘░░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░└────────────────────────┘░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
The last character of mail archive extensions ('counter', .??X)
When we talk about ARCmail we mean the files that consist in the
final result of FastEcho: the files which are ready to be sent to remo-
te systems. These files consist in sets of archived mail packets ha-
ving particular names. As usual they have name and extension; the name
is represented in an alphanumeric number having 8 characters, the ex-
tension which has 3 characters, instead, is subdivided into two parts:
The first two characters are the day of the week abridgement (I.E. "MO"
for Monday ,"TU" for Tuesday "WE" for Wednesday and so on until "SU"
for Sunday), the last one is a progressive number that, for some mail
processor can range from 0 to 9 in decimal mode (that's the ARCmail
standard), some other uses hexadecimal notation: from 0 to 9 and from A
to F and a strict minority of mail processor support also alphanumeric
───────────────────────────────────────────────────────────────────────
- 31 -
FastEcho MANUAL - Tutorial - System dropdown menu -
───────────────────────────────────────────────────────────────────────
notation using characther from 0 to 9 and from A to Z.
With these options you can decide to bind FastEcho to use certain
range convention while creating its ARCmail bundles and within which
range it has to consider an incoming ARCmail bundle valid or not.
5.4.8.1 - Archive extensions (Inbound)
With this toggle you can filter whatever kind of mail bundles ex-
tensions FastEcho has to consider valid or not depending on your prefe-
rences. You can choose among three items: "0-9", "0-9&A-F" and "0-9&A-
Z". The ARCmail standard is only the "0-9" value but you could decide
differently, according to your uplink's conventions.
5.4.8.2 - Archive extensions (Outbound)
This switch, instead, has the task to fix the range that the exten-
sions your locally-created ARCmail bundles will have. Here also you
have the same choice as in 5.4.8.1 paragraph: "0-9", "0-9&A-F" and "0-
9&A-Z". Always remember that the ARCmail standard is only the "0-9"
operating modality.
5.4.8.3 - Mailer's semaphores (check)
We have already talked about semaphores in several occasions within
this tutorial (see 5.4.7.10 and 5.4.4.8). Well, this other option tells
FastEcho to check, or not, the semaphore-file generated by your mailer
in order to preserve the security of your system when working in a mul-
tiline or multitasking environments. In particular, here, it can detect
the mailer semaphore necessary to see if a system is currently online
while FastEcho is starting to add new mail in one bundle addressed just
to this system. In this case FastEcho has to skip (and, if possible it
will) the online system to avoid potential loss of data. This option
works only in commercial FrontDoor, InterMail or Binkley-compatible en-
vironments. In this tutorial we assume that you're working in single-
task, singleline environment, so, you can leave this item to "No"
unless you are perfectly aware of what you're doing.
5.4.8.4 - Mailer's semaphores (create "In session")
That's another semaphore feature. By means of this function you can
let FastEcho generate semaphore files, that are compatible with some
specific mailer environments, to prevent an outgoing call addressed to
the system "x" from taking place while FastEcho is engaged in adding
mail to the ARCmail bundle just addressed to the "x" system. Likely the
previous option seen in the 5.4.8.3 paragraph, the present is useful to
avoid loss of data. As before you can safely leave this item to "No"
unless you are perfectly aware of what you're doing and need it.
───────────────────────────────────────────────────────────────────────
- 32 -
FastEcho MANUAL - Tutorial - System dropdown menu -
───────────────────────────────────────────────────────────────────────
5.4.8.5 - Kill stray attaches
When an ARCmail bundle is ready to be sent, it has an ARCmail at-
tach located in the Primary NetMail Area. Once your mailer sent this
ARCmail bundle to the destination system, normally, its ARCmail attach
will be removed and the archive will be left as a truncated file. By
enabling this option, FastEcho will delete (ignore in Binkley-
compatible environments) all file-attach messages pointing to a non-
existing (due to error or special treatment) or 0-length ARCmail file.
If you have followed this tutorial until now, then toggle this item
"On".
5.4.8.6 - Unpack Unprotected
This switch can enable the FastEcho-Unprotected ARCmail packets
handling feature. With this option turned to "Yes", FastEcho will try
to unpack the ARCmail bundles received by your mailer during
"Unprotected Mail Sessions".Be aware, that such archives might contain
mail-bombs, so unless you're perfectly aware of your system's stability
set this to 'No'. (See also the paragraph 5.4.4.4).
5.4.8.7 - Check complete files
The "Check complete files" option is a very useful function that
could, in several circumstances, allow you to save a lot in your te-
ephone-service bill; how!? That's quite simple. Activating this item;
is enough! But how does it works? Well, when you call your uplink, it
could happen that you aren't able to draw the entire mail-bundle
addressed to you because of interferences, loss of carrier, line noise
and so on. With this switch activated, the partially received bundle
will be completely skipped allowing you to retry the call operation
relying on the Zmodem resume feature in order to complete the
previously interrupted mail session. In this way you can always save
the expenses of redrawing the mail-bundle from its beginning. In our
tutorial, now it's obvious, we shall switch this function active.
5.4.8.8 - Max. compression ratio
That's a security function. It is useful if you want to check if the
incoming bundles contain a mailbomb (which means: a lot illegal
messages which contain the same text and thus can be compressed at a
very high level). To perform this operation FastEcho checks them,
before tossing, for the mail pakets held therein; If it verifies that
the compression ratio of this mail-bundle is higher than x:1 (while the
normal compression ratio is somewhere between 2:1 and 7:1 values), then
FastEcho will discard this archive. In the beginning you better leave
this item as it is.
.-.-.
Here you have completed the "ARCmail option" setup. Now press the
"ESC" key to return to "System DropDown menu".
───────────────────────────────────────────────────────────────────────
- 33 -
FastEcho MANUAL - Tutorial - System dropdown menu -
───────────────────────────────────────────────────────────────────────
5.4.9 - FEUTIL parameters
-----------------
In this section you can adjust all the default values you wish
FEUTIL: the FastEcho companion utility, to take in due consideration
when it is invoked from the DOS prompt. To access these settings, posi-
tion the highlighted box on "FEUTIL Parameters" item and slam on return
key. You will see the following window:
FESetup System Data Export Import F1 Help
░░░░░░░░░░░░░┌────────────────────────┐░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░│ Network addresses │░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░│┌───── FEUTIL Parameters ────┐░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░││>PURGE - Messages< 150 │░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░││ Days 30 │░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░││ Rcvd Days 30 │░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░││ Use arrival date No │░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░││ Autorenumber at 0 │ 1.46 ░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░││ Exclude Users No │░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░░ Copyrigh││ Exclude SysOps No │ All rights reserved. ░░░░
░░░░░░░░░░░░░││ Include USERS.BBS No │░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░││ Keep NetMails No │░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░││ Kill grunged date No │░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░└└────────────────────────────┘░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
Default for FEUTIL PURGE: Keep at max. XXX messages/area; 0 = ignore
5.4.9.1 - PURGE defaults
The next three items, are relative to the standard limitation that
FEUTIL must observe while performing the "purge" operation on your mes-
sagebase. Currently FEUTIL supports the purging function on Hudson, JAM
and *.MSG messagebases. But what's the "purge" operation? The "Purge"
is a maintenance task that has to be done periodically on your message-
bases. Physically it consists in marking messages for deletion under
specific circumstances that you may specify here. The "purge" operation
doesn't phisically remove the messages from your bases but only mark
them to let another different tool perform the physical removal after-
wards (that's the PACK which we'll see later).
5.4.9.1.1 - PURGE - Messages
Here you may specify the number of messages do you want to be kept
in every board after the "Purge" operation has been performed. FastEcho
will mark for deletion the messages that exceed this limit starting
from the older ones. Every board, of course, may have different "purge"
specification but the present will be taken in due consideration when
not differently specified. This number may vary accordingly to the
maximum number of boards you will define in "Area Manager"; that's be-
cause if you have adopted the HMB as messagebase you will have a number
of messages limited to about 16.000 before the Hudson Message Base goes
in overflow. The Hudson has limitations on the number of board too;
this limit is 200 boards. In the worst case, if you will define 200
Hudson boards, you might set this "Purge Messages" limit to 80 (that's
because 80 x 200 = 16000) so, you should take care of this limitation
adjusting the limit conformly. The Jam/Squish and *.MSG messagebases
doesn't suffer the aforesaid limitation, thus, if your system isn't HMB
───────────────────────────────────────────────────────────────────────
- 34 -
FastEcho MANUAL - Tutorial - System dropdown menu -
───────────────────────────────────────────────────────────────────────
based, then you may specify here whatever number you want. For our
tutorial, specify here "150" that's more than enough for 10 HMB boards.
5.4.9.1.2 - PURGE - Days
With the number specified here you will tell FEUTIL your
preferences about how old the messages in your messagebases has to be
before it can start marking them for deletion (based either on the date
of the message or on the date of its arrival, see below). For our
tutorial I suppose that "14" may be right as value, so, input this
number, press return and go on.
5.4.9.1.3 - PURGE - Rcvd Days
Here you may inform FEUTIL that you allow it to start marking for
deletion all messages which have the 'Received' (= read) older than
specified. Make your choice here. For this tutorial set it to "30" to
keep such messages for a longer time.
5.4.9.2 - Use arrival date
This switch involves JAM areas only. In JAM areas, in fact, Fast-
Echo is capable of storing the time & date when an EchoMail message has
been tossed. If you take this option, then the "Purging" function per-
formed by FEUTIL will consider the date when the message was locally
received instead of the date when the message was originally written.
In our tutorial I suggest to take this option because, sometimes it
happens that, thanks to vicious mail routing, one or more messages
could arrive, as far as your system, really late so that the first time
FEUTIL Purge/Pack will be run it will cause their immediate deletion.
5.4.9.3 - Autorenumber at
The value you may define in this item represents a limit of the
highest number of a message in your HMB messagebase . When this limit
is excedeed then the FEUTIL PACK utility will be automatically
qualified to renumber the whole messagebase. But what is the PACK
operation? As we see later in this manual, it is the way to physically
remove all records previously marked for deletion thanks to the FEUTIL
PURGE utility (see also the 5.4.9.1 chapter). When the FEUTIL PACK
operation is performed from the DOS prompt, if it detects that the
highest message number in the messagebase is greater than the one
specified via this item, then the renumbering will be forced without
the optional parameter "-Renumber" too. For our tutorial, leave this
value at "0".
5.4.9.4 - Exclude Users
We, before, talked about primary and secondary NetMail areas (see
also the 5.1, 5.4.2, 5.4.1.1 chapters) so you are now aware of the dif-
ferences between them You might also have an idea about the capability
of FastEcho to export a NetMail message from the "secondary NetMail
area" to the "primary" by way of the "FastEcho Scan" command and the
power of FEUTIL to import a NetMail message from the "primary" to the
"secondary NetMail area" via "FEUTIL import" command. Well, you must
know that FEUTIL can further automatically exclude some NetMail from
importing them in the "Primary NetMail area" simply by toggling the
───────────────────────────────────────────────────────────────────────
- 35 -
FastEcho MANUAL - Tutorial - System dropdown menu -
───────────────────────────────────────────────────────────────────────
"Exclude User" option to "Yes". If you enable this feature, all the
names defined in the "User Names" section (addressed before in the
5.4.2 chapter) will never be hereafter imported from the "primary" to a
"secondary" NetMail area. You will adjust this switch according to your
need when this tutorial finishes; Now leave disabled the "Exclude User"
toggling this option to the "No" status.
5.4.9.5 - Exclude SysOps
This switch is similar to the previous "Exclude User",the only dif-
ferece is that "Exclude SysOps" prevents the "FEUTIL import" command
from importing, from the "Primary" to "Secondary" NetMail area, the
private mail (NetMail) addressed to the names of the SysOps defined in
"Node Manager" section (that we'll see later in this manual). For this
tutorial leave this option disabled, toggling it to the "No" status.
5.4.9.6 - Include USERS.BBS
If this option is switched to active status (Yes), the FEUTIL Im-
port feature (see 7.10 chapter) will always use directly your USERS.BBS
file as include list even if not specified in the FEUTIL Import com-
mand-line. Using this may be useful for BBS systems only. In this way,
the USERS.BBS file will only be read if there are,actually, messages
that could be imported and not always at start-up, as it would in case
of an -INCL list. For our tutorial leave this option disabled unless
you are working with a BBS system.
5.4.9.7 - Keep NetMails
After the NetMail messages are imported from "Primary" to "Secondary"
NetMail area, by means of the "FEUTIL import" command, the original
NetMail messages are automatically removed. By taking this option,
instead, you can bind "FEUTIL import" to copy (not move) the NetMail
message from Primary to Secondary NetMail area, without erasing the
originals. You, further, will be able to import again these already-im-
ported NetMails by using the "FEUTIL Import" command with the "-FORCE"
switch. In this tutorial leave this item with the "No" status.
5.4.9.8 - Kill grunged date
With the use of this switch you will qualify FEUTIL PURGE to mark
for deletion all messages having bad date (I.E. 30-02-94 or 32-12-94)
or date in the future such as 12-12-2000), otherwise these messages
will be kept in your messagebase. For this tutorial we let FEUTIL keep
these messages; so toggle this switch to "No" status.
.-.-.
Here you have finished the setup of FEUTIL parameters. FEUTIL, of
course, has several other function, but we shall see them later talking
about FEUTIL and its switches separately. Now press the "ESC" key and
follow the tutorial.
───────────────────────────────────────────────────────────────────────
- 36 -
FastEcho MANUAL - Tutorial - System dropdown menu -
───────────────────────────────────────────────────────────────────────
5.4.10 - Compression Programs
--------------------
FastEcho, in order to create mail bundles (are so called the archi-
ved mail packets ready to be sent or picked up) has to use almost one
archiver (as known as compression program). In this section you must
define your available archivers to make it possible FastEcho to use
them. Move the highlighted box upon the "Compression programs" item and
press return. After selecting the platform you want to edit the
definitions for (you can define different commandlines for DOS and OS/2
archivers) you will see the following screen:
FESetup System Data Export Import F1 Help
░░░░░░░░░░░░░┌────────────────────────┐░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░│ Network addresses │░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░╔════════════════════ Compression Programs ════════════════════╗░░░
░░░║ Tag Command List Rt.║░░░
░░░║──────────────────────────────────────────────────────────────║░░░
░░░║ 1 ARC Arc.Exe aw @ 18 ║░░░
░░░║ 2 ARJ Arj.Exe a -y -e ! 34 ║░░░
░░░║ 3 ZIP PkZip.Exe -ao @ 34 ║░░░
░░░║ 4 LZH LHa.Exe a -m1 @ 29 ║░░░
░░░║ 5 PAK Pak.Exe a /wa /st @ 30 ║░░░
░░░║ 6 SQZ Sqz.Exe a /p3 @ 34 ║░░░
░░░║ 7 RAR Rar.exe a -y -ep _std @ 35 ║░░░
░░░║ 8 UC2 UC.Exe a -bf @ 40 ║░░░
░░░║ 9 ║░░░
░░░║ 10 ║░░░
░░░║ 11 ║░░░
░░░║ 12 ║░░░
░░░╚══════════════════════════════════════════════════════════════╝░░░
░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
As you can see, several archivers are already predefined. These ar-
chivers are identified through their "Tag" which is the "extension"
that generally these archivers produce or their name. If you need to
insert a new archiver here, remember to insert in the "Tag" column the
typical extension that identifies the archiver, in the "Command" column
the archiver executable program followed by all the switches needed to
perform the right mail-packets compression, In the "List" column you
must type one symbol (it isn't always the same) that identifies the
list of files to be compressed in the same archive. You have the choice
to insert several new other different archivers in this list, if you
need them, and, further, you can modify all the predefined commands of
the still present ones, conformly with your needs. Naturally, the
archiver that you use mustbe present and accessible through your "DOS
PATH". For the tutorial, of course, we shall leave these "archive-tags"
and "commands" as they are (infact they are still rightly configured
and are more than enough too). For every archiver you must define also
the "list prefix" character, used by the specific archiving tool,
allowing the packer to handle multiple *.PKTs in one ARCmail bundle in
a single pass, saving a lot of time. The last column is the "Rt":
Average Ratio; that we shall see in the next paragraph separately.
───────────────────────────────────────────────────────────────────────
- 37 -
FastEcho MANUAL - Tutorial - System dropdown menu -
───────────────────────────────────────────────────────────────────────
5.4.10.1 - Rt. Values in compression programs
----------------------------------
In case you want use the FastEcho ARCmail sizing feature (see also:
5.4.6.6 and 5.5.1.7.1) you ought to specify, in the Rt. column, the
average compression ratio for each archiver. The average value must be
specified in tenth (for example, an average of 1:3.5 means 10:35, so,
you have to enter "35" as value in Rt. column). This value is cal-
culated by overall "Size of PKTs" included in a bundle, divided by the
"Size of resulting archive". Once these parameters are correctly defi-
ned and inserted in these items, FastEcho will try to pack as many PKTs
in one archive by calculating the expected compressed size, according
to the ratio level specified. If the calculated value exceeds the se-
lected maximum, it will call the archiver. It can also happen that, by
mistake, the ratio specified in "Rt." is effectively too low. This will
result in a final archive smaller than the maximum; in this case Fast-
Echo will try to handle that by adding more PKTs to it but the resul-
ting archive but only if the difference between the "calculated size"
minus "current size" will be smaller than the difference than "maximum
size" minus "current size", so that it will create slightly bigger
archives rather than significant smaller ones. In any other case
FastEcho will create a new archive. In order to allow FastEcho to work
as efficent as possible, you ought to tune the "Rt." values for each
archiver configured. If you leave in the ratio field the "0" value, the
average compression ratio will be automatically defaulted to 32 (which
match the 1:3.2 ratio). Here below there are some suggested values for
the most common archivers when they work in standard compression mode.
┌───────────────┬───────────────┐
│ Archiver Rt.│ Archiver Rt.│
├───────────────┼───────────────┤
│ UC2 │ 40 │ ARJ │ 34 │
│ LZH │ 29 │ SQZ │ 34 │
│ RAR │ 35 │ ARC │ 18 │
│ ZOO │ 20 │ LHA │ 32 │
│ ZIP │ 34 │ PAK │ 30 │
└───────────────┴───────────────┘
The shown values, of course, may vary depending on what kind of
mail you currently process (FidoNet, Internet newsgroups etc.); in this
case you can find the better "Rt." value by checking your outbound
archives.You furthermore ought to tune the "Maximum .PKT size" too (see
chapter 5.4.6.4), in order to obtain somewhat constant final archive
size.E.g. it makes no sense to have FastEcho create 2MB big .PKT files
and then have it trying to archive them into a 100kB archive. Basically
it's a good advice to set your Maximum .PKT size to a 1/3 or 1/4 of
your selected maximum archive size. When you have finished press the
"F10" key to save what your have eventually changed and return to
"System DropDown menu".
A word of wisdom
================
Is adviceable to avoid the archivers from setting the archive-time-
stamp to the time/date of the 'youngest' included file, so if one or
more of your archiver command line already contains such a switch,
remove it.
───────────────────────────────────────────────────────────────────────
- 38 -
FastEcho MANUAL - Tutorial - System dropdown menu -
───────────────────────────────────────────────────────────────────────
5.4.11 - Decompression Programs
----------------------
Thanks to this function, FastEcho will be able to detect the type
of archiver that your uplink used to create the ARCmail bundles before
sending them to your system; in this way, FastEcho can automatically
select and use the right unarchiver program needed to decompress them
before processing the contained mails. Select the "Decompression
Programs" item and strike the "return" key. After selecting the
platform, the following layout will appear on your screen:
FESetup System Data Export Import F1 Help
░░░░░░░░┌────────────────────────┐░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░│ Network addresses │░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
░╔═════════════════════ Decompression Programs ═════════════════════╗░
░║ Type Command Calling convention ║░
░╟──────────────────────────────────────────────────────────────────╢░
░║ Unknown ║░
░║ ARC Arc.Exe xwo 0 ║░
░║ PKARC PkUnPak.Exe -xr 0 ║░
░║ PAK Pak.Exe e /wa /st 0 ║░
░║ ARC+Plus Xarc.Exe 0 ║░
░║ ZOO Zoo.Exe xo 0 ║░
░║ PKZip PkunZip.Exe -o -ed 0 ║░
░║ LHarc LHa.Exe e -m1 0 ║░
░║ ARJ Arj.Exe e -y 0 ║░
░║ SQZ Sqz.Exe e /p3o1 0 ║░
░║ RAR Rar.Exe e -y -std 0 ║░
░║ UC2 UC.Exe e -bf 0 ║░
░╚══════════════════════════════════════════════════════════════════╝░
░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
Note that several types of unarchiver are already defined and pre-
configured. In the column to the left are identified the types of ar-
chivers that FastEcho can automatically recognize (this column is pre-
defined so you cannot modify it). In the right column, instead, you may
insert or modify the unarchivers names, conformly with the items pre-
sent to the left in the same row, followed by all their needed swit-
ches. Take note that the very first item, located at the top of the
window, reports "Unknown" as unarchiver type: this means that when
FastEcho starts to decompress the incoming mail bundles, firstly it
tries to recognize the compression methods comparing the mail bundles
archiving type with the FastEcho predefined ones (this you can see to
the left column in this screen) and only after, if all the predefined
types fail the match, then try to decompress it with the "Unknown" type
unarchiver. So, you could agree with your uplink, an archive type dif-
ferent from the FastEcho predefined ones; in this case you must define
in the "Unknown" slot the program's name you agreed with your uplink,
specifing the executable file that will be run and the relatives swit-
ches. In all cases, the unarchiver program that you will use might be
available directly or throughout the "DOS PATH". In our tutorial, once
you are sure to have understood the meanings of every item, the best
thing would be to leave initially this layout untouched. Press "F10" to
save your entry and return to the "System DropDown" menu.
───────────────────────────────────────────────────────────────────────
- 39 -
FastEcho MANUAL - Tutorial - System dropdown menu -
───────────────────────────────────────────────────────────────────────
5.4.11.1 Calling conventions
When calling a decompression program, FastEcho has to tell the
program which files to extract and where to put them, but unfortunately
not all programs use the same conventions for this. By default,
FastEcho has the right convention internally hard-coded for the
predefined programs, but in some rare situations (for example when
using different programs like InfoZip's UNZIP instead of PKUNZIP, UNARJ
instead of ARJ E, etc.) they don't match. So you can tell FastEcho
explicitly which convention (command line format) it has to use for
that program and override the internal default. After you defined the
Decompressor "Type" and "Command", in fact, you will be able to define
the needed calling convention by means of the following selector which
will pop-up when the cursor falls in the "Calling Conventions" column:
┌────────────────┐
│>Default <│
│ cd <path> │
│ <path> *.PKT │
│ *.PKT <path> │
│ *.PKT #<path> │
│ *.PKT -d<path> │
└────────────────┘
the appropriate calling can be selected, as usual, by moving the high-
lighed box and pressing return to confirm. In this way, in the "Calling
convention" column will be reported the type of calling you selected in
numeric form. (I.E. '0' for 'default', '1' for 'cd <path>', '3' for
'<path> *.PKT' and so on. if nothing (= '0') is selected, FE will use
its internal predefined values. For the tutorial leave initially all
the "calling convention" items to their default values ("0") and Press
"F10" to save your layout entry, returning to the "System DropDown"
menu.
5.4.12 - External programs
-----------------
This feature is useful when you need to run one or more external
programs just after FastEcho has unarchived (Unpack) your incoming mail
bundles and/or just before it has to begin archiving (Pack) your out-
going mail packets.In both of them you may specify the full command-
line including all kinds of switches, and the full path too (the path
is only needed if the specified program cannot be found through your
"DOS PATH" environment variable) further you may specify a "batch file"
instead of an executable program. It's also possible to specify here
the macro $[COMSPEC] or any other macro definitions instead of the
program name. Let's now see these two options. Highlight the "External
programs" item and press the "Return key".
FESetup System Data Export Import F1 Help
░░░░░░░░░░┌────────────────────────┐░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░│ Network addresses │░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
░░╔══════════════════════ External Programs ═══════════════════════╗░░
░░║ After Unpack:_ ║░░
░░║ Before Pack: ║░░
░░╚════════════════════════════════════════════════════════════════╝░░
░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
───────────────────────────────────────────────────────────────────────
- 40 -
FastEcho MANUAL - Tutorial - System dropdown menu -
───────────────────────────────────────────────────────────────────────
5.4.12.1 - External programs (After Unpack)
In this field you may define an utility (program or batch file)
which will be run automatically after FastEcho finishes the unpacking
operation of the incoming mail bundles (during the execution of the
"FastEcho TOSS" command). In this way you can process intermediately
all incoming mail packets (*.PKT) in order to obtain, for example, sta-
tistical reports, packets pre-sorting, splitting of large mail packet
files and so on. Be careful to keep in due consideration that the ex-
tracted mail packets may reside in different directories according to
the directory you specified in "Pathnames" section for "Inbound",
"Temporary Inbound" and "Local Inbound". For our tutorial, leave this
field empty.
5.4.12.2 - External programs (Before Pack)
This option is very similar to the previous one, the only differen-
ce is that, the present, will call an external program (or batch file
too) just before the archiving operation of the outgoing mail packets
will take place. Hereby, also, you may specify the program by writing
only its executable name and, if needed, all its switches; you could
define the pathnames too, but it's suggested only if the called program
cannot be found in the current directory or through your "DOS PATH" en-
vironment variable. Be careful because some PKT's utilities and prepro-
cessors operate on the mail packets having the *.PKT extension only,
while, in this case, the outgoing mail packets are in intermediate sta-
tus already having a *.QQQ extension. For our tutorial, leave this
field empty.
5.4.13 - Group names
-----------
This is one great FastEcho convenience: the power of creating pre-
established groups in order to make the area definitions easier for
your EchoMail, local and, if you want, NetMail areas too; furthermore,
the group names definition, will allow you to perform global changes in
the settings of your defined EchoMail, local and NetMail board, by
groups. By now highlight the "Group names" item and press the return
key.
FESetup System Data Export Import F1 Help
░░░░░░░░░░░░░┌────────────────────────┐░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
╔══════════════════════════════ Groups ═══════════════════════════════╗
║ Name Name ║
╟─────────────────────────────────────────────────────────────────────╢
║ A) - FidoNet EchoMail Natl Q) ║
║ B) - FidoNet EchoMail Intl R) ║
║ C) - ZyXELnet EchoMail Area S) ║
║ D) - Local BBS Area T) ║
║ [...] [...] ║
║ P) 6) ║
╚═════════════════════════════════════════════════════════════════════╝
░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
In this layout you may define up to 32 group names for as many groups
of areas you have. These names will be considered later for selecting
───────────────────────────────────────────────────────────────────────
- 41 -
FastEcho MANUAL - Tutorial - System dropdown menu -
───────────────────────────────────────────────────────────────────────
the appropriate area defaults. In our tutorial we have one main address
and one aka so, we might define at least one group name for each net.
You may furtherly subdivide the same net into two different groups
(I.E. the former as "ThisNet national area" and the latter as "ThisNet
international area") for your convenience. For our tutorial we shall
define four group names. We are assuming to have one main address for
Fidonet and an "AKA" for ZyXELnet. The minimal number of group names we
must define is two but, for our convenience, we want to split the
Fidonet EchoMail areas into two different group names: the first for
the national-EchoMail and the second for the international-echomail.
Last of all, you need at least one "local" area group name
Place the cursor upon the "A)" item and press the "return" key,
then input herein: "FidoNet EchoMail Natl" and press the "return" key
again. this, hereafter, will be the name of the group relative to all
the national Fidonet EchoMail; Position the cursor upon the "B)" item,
press return, and type "Fidonet EchoMail Intl" confirming with the
"return" key again. This will be the name of the group relative to all
the international Fidonet EchoMail. (Repeat the aforesaid operations
until you have completed on your screen, the layout you can see in the
above picture) and then press the "F10" key to save your entry and go
back to the "System DropDown Menu".
5.4.14 - Origins
In this section you will have the option to insert one origin line in
your EchoMail messages only. You cannot insert it in a NetMail message
because it's useless; in order to understand why,let's see now the
differences between EchoMail and NetMail (aka Matrix) messages.
5.4.14.1 - EchoMail vs. NetMail (matrix)
5.4.14.1.1 - EchoMail
--------
An EchoMail is a public message. It means that you may also address
an EchoMail to someone in particular but, ANYONE can read your message
freely (and answer you too). The EchoMail messages written by sysops,
points or users aren't certainly untidily sent and gathered together in
one single container; in the countrary! They must be written, sent and
read grouped by specified "topic". So, any EchoMail group (that
hereafter we'll call "area or board") has a description that specifys
the main argument (Topic) that all the messages contained therein must
follow; thus, when you answer an EchoMail message or when you write a
new one, you aren't answering to one the user in particular, but, you
are answering to all the user in the board you are writing in. The
sender net-address of any EchoMail message isn't reported in its header
because it's useless, so in order to publicize what is the net-address
of the original sender, any user has to insert on a new line at the
bottom of the message, after the "Tearline" (see also: 5.4.7.1 and
5.4.7.2 paragraph), one line called "Origin" that begins with an
asterisc (*) followed by one space, the word "Origin: ", the system
name and, finally, the net address of the sender. It will look like
this sample:
───────────────────────────────────────────────────────────────────────
- 42 -
FastEcho MANUAL - Tutorial - System dropdown menu -
───────────────────────────────────────────────────────────────────────
From: Reed Richards
To : All
Subj: Question
--------------------------------
[...]
Message text
[...]
--- FastEcho 1.46+
* Origin: Test System (2:999/999)
---------------------------------
5.4.14.1.2 - NetMail
-------
NetMail messages are, instead, somewhat private. Any NetMail messa-
ge has to be addressed to one single user having one single net ad-
dress. A NetMail message can, generally, be read only by you and by the
receiver, so, the receiver has to know, directly, who is the sender and
what net-address he has, in order to answer him quickly, further, to
perform the NetMail routing, a system need to immediately know the net-
address of the message addressee, thus, his address is specified in the
message header directly, thus, repeating it in an eventual origin line
would be absolutely useless. A NetMail message will look like the fol-
lowing sample:
From: Reed Richards (2:999/999)
To : Marco Piazza (2:2448/400.7)
Subj: Question
--------------------------------
[...]
Message text
[...]
--- FastEcho 1.46+
---------------------------------
Returning to the "Origin" line argument, let's now see how you can
define them in FESetup. Higlight the "Origins" item, which is the last
one in the "System DropDown Menu" and strike return. You will see the
following layout.
FESetup System Data Export Import F1 Help
░░╔════════════════════════════ Origins ══════════════════════════╗░░░
░░║ 1 This is the Reed's system ║░░░
░░║ 2 System in test@Fidonet.org ║░░░
░░║ 3 System in test@ZyXELnet.ftn ║░░░
░░║ 4 [...] ║░░░
░░║ 20 ║░░░
░░╚═══════════════════════════════════════════════════════════════╝░░░
░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
Press F10 to save or ESC to abort editing...
An "Origin" line, of course, must not contain useless data, so make
sure to insert herein, only the information necessary to rightly
identify only your system name which may be the "Bulletin Board System"
name or the "Point System name". You may define in this layout as many
different origin lines as you need, with the maximum of twenty entries;
later, in the area-definition chapter, we shall see that, for every
───────────────────────────────────────────────────────────────────────
- 43 -
FastEcho MANUAL - Tutorial - System dropdown menu -
───────────────────────────────────────────────────────────────────────
board, you will be able to choose among all the origin line you defined
here, according to your needs. For our tutorial we shall define three
different origin lines. Place the cursor onto the "1" item and press
"return". Finger, in the highlighted field: "This is the Reed's system"
and press "return" again. place the cursor to next item and press re-
turn, then input: "System in test@Fidonet.org" without quotes. In this
case you defined one origin line that informs other systems that you
are in test, the "@" symbol (aka ampersand) works as separator, the Fi-
donet.org is the domain (naturally you might use this origin line only
in Fidonet boards); then press "return". Go over the "3" items and
strike "return";type herein "System in test@ZyXELnet.ftn". Like the
previous, this origin line describes that your system is in test but
you might use this one in "ZyXELNET" boards. Press "return" when fini-
shed. When defining the "Origin" lines make sure not to insert your
net-address because it will be automatically added.
.-.-.
Here you have completed the compilation of the "Origin" line
definitions and the "System" section too. Press now the "F10" Key to
save your entry returning in "system DropDown menu", then press the
"ESC" key to return to the "Topbar DropDown Menu". The highlighted box,
now, will be on the "System" item; press the "right-arrow" key and pla-
ce the highlighted box upon the "Data" item, strike the "Return" key,
so that, the "Data DropDown Menu", will be shown to you.
5.5 - Data DropDown Menu
==================
FESetup System >Data< Export Import F1 Help
░░░░░░░░░░░░░░░░░░░┌─────────────────────┐░░░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░░░░░░░│>Node-Configuration< │░░░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░░░░░░░│ Group Area Defaults │░░░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░░░░░░░│ Area-Configuration │░░░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░░░░░░░│ Carbon Copies │░░░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░░░░░░░│ AreaFix Options │░░░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░░░░░░░└─────────────────────┘░░░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░░░░░░░░░░░░░ FastEcho; Setup 1.46 ░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
Call Node-Manager ...
You have now entered in the "Data" section of FESetup. Here we'll
see how to configure the nodes (or point) that will call your system to
pick up and send their mail to you (downlinks) and the nodes that you
will call in order to draw and send your daily mail (uplink); then we
shall configure the "Area Defaults" which is another convenient tool
that may save a lot of your time when you enter in the next option: The
"Area-Configuration".In "Area-Configuration" we shall define all the
EchoMail, NetMail and Local areas where you will receive your daily
mail. We shall see the "Carbon Copies" too, that is a special FastEcho
───────────────────────────────────────────────────────────────────────
- 44 -
FastEcho MANUAL - Tutorial - Data dropdown menu -
───────────────────────────────────────────────────────────────────────
feature capable of copying in one special board, all the messages that
match some characteristics which you will define. Lastly, we shall see
the "AreaFix-Option" popup menu. AreaFix is an automated system capable
of making it possible for your downlinks to remotely adjust its parame-
ters themselves, without your manual intervention. For our tutorial I
assume that you have two uplinks (2:999/900 for FidoNet, the SysOp name
of this node will be Ben Grimm and 16:999/900 for ZyXELnet, the SysOp
name of this node will be Sue Wright), furthermore you will have one
point as downlink (2:999/999.1 for fidonet where the operator name is
Franklin Richards).Let's now see each one of these options in detail.
5.5.1 - Node Configuration
------------------
In the "Node Configuration" section you must define all the remote
system that you call for mail (uplink) and the systems you are called
from (downlinks) with all their parameters, SysOp names, Akas, ARCmail
and AreaFix passwords and so on. In our tutorial you must define two
nodes and one point. Place the highlighted box upon the "Node Configu-
ration" item and press the return key. Now you have in front of you the
layout shown in the picture below.
FESetup System Data Export Import F1 Help
░░░░░░░░░░░░░░░░░░░┌─────────────────────┐░░░░░░░░░░░░░░░░░░░░░░░░░░░░
░╔══ 1/1 ═══════════════════ Node-Manager ══════════════════════════╗░
░║ Addresses ║░
░║ Main: 2:999/900.0 4D/Type 2+: Y ║░
░║ ARCmail: 2:999/900.0 TosScan: N ║░
░║ ARCmail 0.60: N ║░
░║ Name: Ben Grimm Pack priority: 0 ║░
░║ Convert Umlaut: N ║░
░║ Your Aka: 2:999/999.0 ║░
░║ Allow Area-Create: Y ║░
░║ Passwords New Area Default Group: B ║░
░║ Packet: Export By Name: N ║░
░║ AreaFix: THETHING ║░
░║ Status AreaFix flags: » ║░
░║ ARCmail: None ║░
░║ AreaFix: None Send Notify: Y ║░
░║ Packer: ZIP Max. size: 0 Send Help: Y ║░
░║ ║░
░║ Groups: AB Passive: N ║░
░║ Security: 100 Automatic Passive: 0 ║░
░╚══════════════════════════════════════════════════════════════════╝░
Enter-Edit Ins-Add Del-Delete F2-Rout F5-Browse F4 Area List F5-Copy
The one you are looking at now on your video display is empty, of
course, but we will dress it soon. We shall begin to define the first
node: the fidonet one (2:999/900) (You will call this node to receive
your fidonet mail). Well, you are now in "view" mode. In this modality
you can run through all your defined nodes checking their parameters
(when they are defined). Take now a glance to the last row at the
bottom of the screen, you will see a group of keys: "Enter", "F2"
through "F5", "Ins" and "Del". These are the keys which are active
before entering in editing mode. In order to insert your first node
press now the "Ins" key: "New Entry". The cursor will be automatically
placed upon the first item of the screen: The "Main Address".
───────────────────────────────────────────────────────────────────────
- 45 -
FastEcho MANUAL - Tutorial - Data dropdown menu - Node Configuration -
───────────────────────────────────────────────────────────────────────
5.5.1.1 - Main Address
In this field you must type the net address of the node you are
defining. It represents its matrix-address that will be used by Fast-
Echo for all its communication with the aforesaid. This address will be
further checked when FastEcho will processes all incoming mail packets
and when it performs the AreaFix automated operations requested from
this node. For our tutorial type the address "2:999/900" which is your
"uplink" one; then press return to go to the next item.
5.5.1.2 - ARCmail
We extensively spoke before about ARCmail (see: 5.4.8 and 5.4.4.6
paragraphs) so, I assume that you are now sufficently aware of it. This
ARCmail item represents a convenience function. Normally, the address
inserted here, is a copy of the main address seen before, but, in some
occasions, it may be different. For Example: If you are part of two
different nets and one of your downlinks has the same nets linked to
you, than, normally FastEcho creates two different ARCmail bundles (one
for each net) because it rightly considers two different addresses as
two different systems but, as a matter of fact, it's not true because
in this case, the same system has both akas. With this ARCmail address
you can make FastEcho aware of that. Pratically it will archive the
mail for this system in one single ARCmail bundle containing mail pa-
ckets for both akas. In this way you can save some space on your hard
disk and have fewer file-attaches. This doesn't mean that you can
define this system in node manager only once. You should define this
system twice, for both akas and for both of them you will specify the
same ARCmail address. For our tutorial we won't need this feature,
thus, we shall leave this item with the same address defined in "Main
Address".
5.5.1.3 - Name
In this field you must input the SysOp's first and second name of
the node with address defined in 5.5.1.1; make sure to input its name
correctly so, if you wish, you can use the "Exclude SysOps" feature
seen in the 5.4.9.5 chapter. Confirming the SysOp name with the
"return" key you will be positioned directly on "Your AKA" item.
5.5.1.4 - Your AKA
When the cursor falls in "Your AKA" item, the following popup
window will be shown:
┌──────────────┐
Your Aka:│>2:999/999.0< │
│ 16:999/999.0 │
└──────────────┘
This is the item where you must choose the aka (corresponding to
your matrix address) you wish to use for the node you are defining. Na-
turally you must select the aka that you agreed on with the uplink or
downlinks you will send/forward mail, accordingly with the net you are
working into. Make sure to select the right one here. For our tutorial,
with the "arrows-key" move the highlighted box upon the 2:999/999 ad-
dress and strike the return key.
───────────────────────────────────────────────────────────────────────
- 46 -
FastEcho MANUAL - Tutorial - Data dropdown menu - Node Configuration -
───────────────────────────────────────────────────────────────────────
5.5.1.5 - Passwords
In this section you may define two different passwords. These pass-
words must be in accordance with your uplinks/downlinks and have two
different meanings.The definition of these passwords are for security
purposes only and doesn't impair the FastEcho performances or fun-
ctionalities.
5.5.1.5.1 - Passwords (Packet)
We have already talked about ARCmail several times through this tu-
torial (see: 5.5.1.2, 5.4.8 and 5.4.4.6). In this particular case you
may define one password that will be embedded in your ARCmail bundles
created locally and addressed to your uplink/downlink or that will be
checked in the ARCmail bundles you will receive from the same
uplink/downlink. This operation may be done in order to activate the
"Full Security" we seen in the 5.4.7.14 chapter. If you define a pass-
word to put herein and the "Security" option (see 5.4.7.14) is toggled
to "Full" then this function will be active. If an ARCmail bundle co-
ming from your uplink/downlink fails this FastEcho's inspection, then
it will be refused and left in the "INBOUND" directory renamed as
*.SEC. For our tutorial leave this field blank.
5.5.1.5.2 - Passwords (AreaFix)
This is the password you may agree on with your downlink to make
possible changes on its Node or Areas configuration in an automatical
way, remotely and without any your manual interventions. If you don't
insert any password here, then FastEcho will process undiscriminately
any AreaFix request coming from this downlink; if you will put a pass-
word in this field that doesen't match your downlink one, then the
AreaFix request will be denied by FastEcho. When, instead, your AreaFix
password matches perfectly the one used by your DownLink then the Area-
fix request will be correctly performed. It's advised to leave free the
option to make AreaFix request only when you are aware that your
downlink has aquired the right knowledge about what AreaFix really
does. The best thing to do is to define in this item one password
without communicating it to your downlink, then, when you are sure that
this one has understood the AreaFix mechanism, you may tell him your
password. For our tutorial put in this field the password "THETHING"
then press return to continue with the farther options.
5.5.1.6 - Status
In the "Status" section you may define the attributes you want that
FastEcho will ascribe to the locally created ARCmail attaches and
AreaFix messages in conformity with the status of this node. The attri-
butes will be different from uplink or downlink status.
5.5.1.6.1 - Status (ARCmail)
As you certainly know, an ARCmail bundle, in order to be sent, has
its ARCmail attach which is a kind of empty NetMail message located in
the "Primary NetMail" directory. The task of this NetMail message is to
carry the ARCmail bundle to your uplink/downlink system; to do so, it
already has a mandatory attribute set: "File/attach" which means that
it has one file (the mail bundle) attached; further it could have other
───────────────────────────────────────────────────────────────────────
- 47 -
FastEcho MANUAL - Tutorial - Data dropdown menu - Node Configuration -
───────────────────────────────────────────────────────────────────────
attributes set. When the cursor falls on this item, the following box
will be shown on your screen:
Status ┌──────────────┐
ARCmail:│>None< │
AreaFix:│ Hold │
Packer:│ Crash │
│ Direct │
Groups:│ Hold/Direct │
Security:│ Crash/Direct │
│ No attach │
└──────────────┘
For example, if the system you are defining now is one of your up-
links you may prefer your ARCmail attaches to have the "Crash" status,
so, that your mailer will automatically call your uplink for sending
your mail. For your downlink, instead, you may prefer to let FastEcho
set the "Hold" status in your ARCmail attach, so, your mailer never
calls to send him the mail but your downlink must call you, instead, to
perform the mail transfer. The method I suggest you is slightly diffe-
rent. I suggest you select in this box the "None" status for ARCmail
bundles, leaving at your FrontDoor router (ROUTE.FD) the task to right-
ly qualify the nodes that you must call, and wait for the nodes that
must call you for mail (you must adjust the statements and the commands
in ROUTE.FD in the correct way of course; refer to your FrontDoor ma-
nual for further information). With the "No attach" item, FastEcho
won't create any ARCmail attaches, but will overwrite the old archive
everytime it has mail to compress (so this is only for special purposes
such as points via LAN etc.). For our tutorial move the highlighted box
to the "None" item and press "Return" to confirm and directly go to the
next item.
5.5.1.6.2 - Status (AreaFix)
This option is similar to the previous one but here will be concer-
ned the attributes that FastEcho will ascribe to its AreaFix reports.
see the picture below:
ARCmail:┌──────────────┐
AreaFix:│>None< │
Packer:│ Hold │
│ Crash │
Groups:│ Direct │
Security:│ Hold/Direct │
│ Crash/Direct │
└──────────────┘
You can choose from several options, according with your needs but,
for this option also, I suggest you select the "None" status leaving to
the router of your mailer the task to handle AreaFix messages and
ARCmail attaches. For our tutorial, place the highlight box upon the
"None" item and strike the return key to confirm and go directly to
next option.
───────────────────────────────────────────────────────────────────────
- 48 -
FastEcho MANUAL - Tutorial - Data dropdown menu - Node Configuration -
───────────────────────────────────────────────────────────────────────
5.5.1.7 - Packer
Position the highlighed box on "Packer" item, you will see the fol-
lowing screen immediately without press the "Return" key:
┌─────┐
│>ARC │
│ ARJ │
│ ZIP │
│ LZH │
│ PAK │
│ SQZ │
│ RAR │
│ UC2 │
│.PKTs│
└─────┘
In order to obtain your maximum system performance, FastEcho al-
lows you to select what compression utilities you wish to be used when
generating mail bundles for this node. After selecting your preferred
compression utility, FastEcho will always use it when preparing mail to
be forwarded to the system you are configuring. Every system defined in
"Node-Configuation" could, of course, have different compression utili-
ties; to select your preferred one, simply move the highlighted box, by
means of the "Up" and "Down" arrow keys, until you reach the compressor
utility you need, then press "return". Be careful that every compres-
sor you select here must be present and reachable by FastEcho, both,
directly or via the "DOS PATH" environment variable. You can, at first,
agree with your uplink/downlink preferred compressor and then select
the right one. For our tutorial we'll select the PKzip. Position the
highlighted box on the "ZIP" item and press the "return" key to con-
firm. You will go directly to the next item.
5.5.1.7.1 - Maximum size
This setting works by fixing the maximum bundle size that FastEcho
is allowed to generate for this node, exactly as the already seen
"Maximum ARCmail size" option treated at the chapter 5.4.6.6, but this
one is more specific because it takes effect upon the actual node only
while the "Maximum ARCmail size" item acts upon all configured nodes
where the "Maximum size" item is left to "0". To fine tune this feature
you must define the "average compression ratio", the "Maximum .PKT size
and the "Maximum ARCmail size" items (read carefully the chapters
5.4.10, 5.4.6.4 and 5.4.6.6). You may set this field to "-1" in order
tell FastEcho to create only one huge archive for that system.
───────────────────────────────────────────────────────────────────────
- 49 -
FastEcho MANUAL - Tutorial - Data dropdown menu - Node Configuration -
───────────────────────────────────────────────────────────────────────
5.5.1.8 - Groups
In the group section you have to define the groups of areas that
your downlink will be able to request to your system through an AreaFix
request. The same groups will be used by FastEcho internally for its
maintenance. When you position the cursor upon the "Groups" item then
the following PopUp-menu will be automatically shown:
┌─────────────────────────────────┐
│>■ A) - FidoNet EchoMail Natl< │
│ ■ B) - FidoNet EchoMail Intl │
│ C) - ZyXELnet EchoMail Area │
│ D) - Local BBS Area │
│ [...] │
│ X) │
│ Y) │
│ Z) │
└─────────────────────────────────┘
The groups listed in this box are the same you defined before in
the "Group Names" section (see: 5.4.13 paragraph). Here, you must se-
lect, by marking them, the areas-group that you want left available to
the downlink which you are defining. This downlink, then, will be able
to link or unlink the available areas sending an AreaFix request to
your system. You can, of course, activate manually other areas belon-
ging to other groups but the operating field of your downlink will be
strictly limited to the group defined herein. To activate the groups,
simply move the cursor upon the desired group that you want to make ac-
tive for this downlink and press the space key; you will see one small
black square to the left of the selected group name. This box means
that the group will be available for this node. To select groups you
may either press the relative key (I.E. pressing the "A" key you will
tag the "A" group), further, you can select all groups with the "ALT-A"
key combination or deselect them with "ALT-C". You might know that
there are some exceptions to this rule, for example, if your downlink
has a security level of 10 and has the "A" group available, but you,
have a particular area belonging to the "A" group that has a minimum
security level of 20, then your downlink won't be able to link this
area because its security level isn't enough. For our tutorial you
haven't any need to define groups for this node because you are confi-
guring one "Uplink" and you will never receive an AreaFix request from
an "Uplink" but, for "Equity" you'll tag it all the same. Press the
letter "A" and the letter "B" until the two fidonet groups are tagged
by the little black square; then press the "ESC" key to return to the
"Node Configuration" layout.
5.5.1.9 - Security
As already mentioned in the previous paragraph, a downlink cannot
link any areas having security level higher that the one specified in
this field; further, this security level, is strictly related to the
groups available to this node. For example: A node has level 10 and has
available the "A" and the "B" groups; this node will request, by means
of AreaFix, an EchoMail area belonging to group "A" but having security
level 11, well, the linking will be denied because of its level; the
same node now wants to link, with AreaFix request, an EchoMail area be-
longing to the group "C", the linking will be denied again because this
───────────────────────────────────────────────────────────────────────
- 50 -
FastEcho MANUAL - Tutorial - Data dropdown menu - Node Configuration -
───────────────────────────────────────────────────────────────────────
node hasn't any access to group "C". A node can definitely link or un-
link any areas IF the area belongs to an authorized group and it has a
security level lower or equal to the Node security level. For the tu-
torial, input here the level 100 and strike the "return" key.
5.5.1.10 - 4D/type 2+
This flag is necessary to define if this node has the "4D" capabi-
lity but what does "4D" mean? It's quite simple: It means four dimen-
sion addressing. A typical "4D" address is composed of four parts: The
Zone, the Net, the Node and, at last, the Point. For example, the ad-
dress: 2:999/999.1 belongs to Zone 2, Net 999, Node 999, Point 1 (for a
better explanation on what means Zone, Net, Node and Point see in the
Appendix A). Thanks to this addressing method any element of the net
can be precisely identified. But there exists another old-fashoned sys-
tem called FakeNet or PointNet system. With this, now obsolete, system,
a point is identified with one address that's typical belonging to a
node but it's a fake because it belongs to a point. If you already use
the PointNet method and if you specified the PointNet clause, in "Net-
work Addresses" (See: 5.4.1 chapter), then you can rely on the Fast-
Echo power to automatically remap the "4D" point into PointNet one. It
means that you can treat your point with its 4D addressing and FastEcho
will do the rest. If you set this option to "N" then only pure FTS-0001
packets will be generated; otherwise, using the normal 4D addressing
FastEcho will be forced to generate mail-packets compatible with the
FSC-0039. For our tutorial set this toggle to "Y".
5.5.1.11 - TosScan
You must consider this toggle if one of your connected systems uses
TosScan 1.0. If the node you are defining in this section uses TosScan
as mail processor and you are running your system in 4D way (see
5.5.1.10) then you should toggle this switch to "Y" status. That's
because, TosScan 1.0 is 4D capable only with itself or with other
TosScan. By Toggling this switch to "Y" FastEcho, while processing the
mail bundles coming from this node, will be forced to use the TosScan-
Product-Code instead of its own. In this way FastEcho will avoid any
compatibility problems. For our tutorial leave this option disabled
assuming that this node doesn't use TosScan.
5.5.1.12 - ARCmail 0.60
It may happen that you have to deal with uplinks that use a
very old standard when tossing mail: The ARCmail 0.60. The old mail
proces-sor that adopts this standard uses a very special naming
convention to perform the toss operation, thus, if you let FastEcho
create and send him ARCmail bundles having new standard conventions,
it will cause er-rors. You have the choice to prevent and solve this
problem simply bin-ding FastEcho to create ARCmail bundles with this
old standard, by tog-gling this option to Y. I suggest you ask your
uplink before switching this option to active because you might use
it only if really neces-sary. For our tutorial we assume that none
of your uplink uses such stone-age tosser,so leave this option not
active with the N status.
───────────────────────────────────────────────────────────────────────
- 51 -
FastEcho MANUAL - Tutorial - Data dropdown menu - Node Configuration -
───────────────────────────────────────────────────────────────────────
5.5.1.13 - Pack priority
This switch defines the priority order to which FastEcho start to
process the mail for one system before the others. This toggle has four
possible values ranging from 0 to 3. The higher this value is the
higher priority this node has. It does mean that the ARCmail for
systems having a level of 3 will be compressed before the ARCmail for
the nodes having a levelo of 2 and so on. Normally,FastEcho processes
mail for the nodes defined in "Node Manager" starting from the one
having a lower address number to a greater one but if one or more,
among your defined node, has set the "Pack priority" level to values
higher than 0, then FastEcho starts to process mail giving the right
priority to them and sorting by node number within them, then it
gradually proceeds to process the mail for the other nodes with lower
priority until it reaches the 0 level. This option can be useful for
systems that handle a lot of mail. In this way they can tell FastEcho
to process mail accordingly to their requirements. The Pack priority
may also speed up the performaces on multiline-based systems; For
example, an HUB can, firstly, compel FastEcho to pack ARCmail for all
his important downlinks and, only after, the mail for his points, so,
while FE is still involved in packing mail for the points, the systems
having the "Priority" flag set are already free to pick up new mail on
another line. For our tutorial leave this toggle to "0".
5.5.1.14 - Convert Umlaut
This feature may be useful for German people only. As you certainly
know, there are some symbols and letters that you cannot use in Echo-
Mail areas. In these forbidden letters are included the, so called,
German Umlauts (ÄäÖöÜüß). If you switch this option to active, then
FastEcho will convert on-the-fly the Umlauts into policy-compliant
characters while exporting messages.
5.5.1.15 - Allow Area-Create
As we saw in the 5.4.7.3 chapter, FastEcho, if you want, has the
power to create automatically the areas that your uplink starts sending
you without your expressed request. The operation that you made in the
5.4.7.3 chapter was only a general operation, intended to activate this
feature but FastEcho needs to be aware of which uplinks are able to do
so. By toggling this option to "Y" status, you will inform FastEcho
that this node has your permission to send new areas to your system
without limitation, thus FastEcho can automatically define, as soon as
it receives it, the new areas in its area definition (area-manager),
creates new folders for your Mailer and creates new areas in your BBS
software; accordingly with "Auto Area Create", "Update Mailer Config"
and "Update BBS config" settings seen in the 5.4.7.3, 5.4.7.4 and
5.4.7.5 chapters. For our tutorial you may leave this option active by
toggling it to "Y".
───────────────────────────────────────────────────────────────────────
- 52 -
FastEcho MANUAL - Using FastEcho -
───────────────────────────────────────────────────────────────────────
5.5.1.16 - New area default group
When FESetup detects the "Allow area create" option active, it will
enable this "New area default group" too, otherwise you will not have
any access to it. If you chose the previous option, then confirming
your selection, the following menu will be shown to you:
┌───────────────────────────────┐
│>A) - FidoNet EchoMail Natl< │
│ B) - FidoNet EchoMail Intl │
│ C) - ZyXELnet EchoMail Area │
│ D) - Local BBS Area │
│ [...] │
│ Y) │
│ Z) │
└───────────────────────────────┘
By means of this feature, in fact, you will be able to select to
what kind of group, the areas that FastEcho automatically creates, will
belong to. For our tutorial you can select the "A" or "B" groups. Place
the highlighted box upon the "A" group and strike the "return" key. To
the right of the "Area default Item" your selected group will be vi-
sible.
5.5.1.17 - Export by name
If you switch this option active by toggling it to "Y" status then
FastEcho will export to this node, undiscriminately, all the EchoMails
addressed to the SysOp's name (defined above. See:5.5.1.3) that it
detects while performing the TOSS and SCAN operations. This applies
also if, the mails addressed to him, belong to areas normally unacces-
sible for this node due to its security level or due to its allowed
groups too. I suggest you leave the "Export by name" option disabled
unless you have very particular needs. If you have followed the tuto-
rial until now then leave this option disabled.
5.5.1.18 - AreaFix flags
Every system configured in your node manager can have personalized
AreaFix settings in order to tune the FastEcho behavior when it pro-
cesses AreaFix requests. By Selecting this item you can access to one
specialized submenù containing all the options needed to allow or deny
to your downlins the extra AreaFix features or, moreover, enable or
disable special AreaFix functions. By selecting the "AreaFix flags"
item you will see the following popup:
───────────────────────────────────────────────────────────────────────
- 54 -
FastEcho MANUAL - Using FastEcho -
───────────────────────────────────────────────────────────────────────
╔════════ AreaFix flags ════════╗
║ ║
║>Allow rescan Yes ║
║ Forward requests Yes ║
║ Send rules Yes ║
║ Allow %FROM No ║
║ Allow area renaming No ║
║ Allow area deletion No ║
║ AreaFix type Standard ║
║ Remote program AreaFix ║
║ Add '+' No ║
║ Add '---' <tearline Yes ║
║ Forward changes No ║
║ ║
╚═══════════════════════════════╝
5.5.1.18.1 - Allow Rescan
This switch can allow or prevent that your FastEcho processes the
%RESCAN MetaCommand eventually found in the AreaFix requests from the
system you are actually configuring. Note that, in order to make this
switch active or not, you must before enable the "Allow rescan" option
in Data->AreaFix Options.
5.5.1.18.2 - Forward requests
As you will see later in this manual, FastEcho under certain condi-
tions (if you have available and configured the list of areas forwarded
from your uplink) is capable to forward an AreaFix request received
from your downlinks to your uplinks. By enabling this switch, FastEcho
will check the AreaFix forward list you set up in "Forward request"
configuration (look at paragraph 5.5.6.13 for details) in order to
complete the operation. By keeping this switch disabled, instead,
FastEcho ignores the MetaCommand %Rescan completely.
5.5.1.18.3 - Send Rules
Every EchoMail area has precise rules that every conference parta-
ker must strictly respect. These rules, also known as "Area Policies",
are collected in several ASCII files. When a downlink requests to your
system the connection of a new EchoMail area FastEcho has the power to
send him the related area-rule-file. This switch allow or prevent
FastEcho to send to this system the conference rule of areas it
requests to be linked. Note that, in order to make this option active
or not, the "Send conference rules" global option (You can find in
Data->AreaFix Option->Send Conference rules), must be enabled.
5.5.1.18.4 - Allow %FROM
The feature provided with the MetaCommand %FROM is also known as
"remote manintenance". It isvery powerful. Using it, anyone (if you
want) can perform several changes in your FastEcho configuration
remotely, simply by sending to your system an AreaFix request having,
as first AreaFix MetaCommand, the "%FROM <Address>" one. By activating
this option you will allow the use of the %FROM metacommand in the
AreaFix requests sent to you by the system you are currently
───────────────────────────────────────────────────────────────────────
- 55 -
FastEcho MANUAL - Using FastEcho -
───────────────────────────────────────────────────────────────────────
configuring. Doing so, from now on, he canperform all the function
provided by all other AreaFix MetaCommands that follow the "%FROM" one
as if they were made by the node specified in the <Address> parameter.
This function could be useful whenever you want leave the upkeep of
your system (i.e.while you are absent) to one full-confidence and
reliance SysOp. For our tutorial leave it to "N".
5.5.1.18.5 - Allow area renaming
The FastEcho AreaFix processor is capable to allow areas renaming
remotely simply by using the symbol "#" in the AreaFix request in the
following way:
#<old_area_tag> <new_area_tag>
If you want that the dowlink you are actually configuring can issue
the area renaming operation upon your system with this method then
toggle this switch to Yes, otherwise disable it toggling it to No. (see
also paragraph 5.5.5.1.24)
5.5.1.18.6 - Allow area deletion
When allowed to upkeep your system a reliance uplink or downlink
can also delete areas from your FastEcho configuration remotely. This
can be done via the special AreaFix metacommand "~" in this way:
~<area_tag_to_delete>
If you want that the downlink you are actually configuring can
issue the area deletion operation upon your system by using this
method, then toggle this switch to "Yes", otherwise leave it on "No"
status. (see also paragraph 5.5.5.1.24)
5.5.1.18.7 - AreaFix type
This option is intended to inform your FastEcho AreaFix on what
kind of AreaFix processor is installed on the remote system you are
actually configuring. It must be done in order to let FastEcho
communicate with it correctly. There are three kind of setting you can
choose here: "Standard", "Enhanced" and "None". Select "None" when the
remote system is a point or, either, when it hasn't AreaFix
capabilities at all. Select "Normal" when the remote system has a con-
ventional AreaFix processor. The "Enhanced" mode can be selected only
if you are sure that the remote AreaFix manager is FSC-57 compliant
(such as FastEcho, Imail and others). Where the "Enhanced" selection is
appliable FastEcho will be enabled to directly use (when communicating
with this system) the special "Delete" and "Rename" AreaFix metacommand
already seen in the previous two paragraphs.
5.5.1.18.8 - Remote program
This flag tells FastEcho what kind of area manager name it must use
when addressing the requests to the remote system you are configuring.
Normally all the area managers are abled to accept "AreaFix" as address
but in some rare cases. Anyway, FastEcho supports the use of other area
manager names which are selectable by means of this switch: AreaMgr,
AreaLink, EchoMgr.
───────────────────────────────────────────────────────────────────────
- 56 -
FastEcho MANUAL - Using FastEcho -
───────────────────────────────────────────────────────────────────────
5.5.1.18.9 - Add '+'
Here you can specify if the remote area manager needs the "plus"
sign just before the area tag in order to link it correctly. FastEcho,
by default, doesn't put it but you can modify the normal FastEcho
behavior by simply selecting "Yes" in this field.
5.5.1.18.10 - Add '---' <tearline>
The tearline (three consecuteve dashes) specifies where the message
text finishes. Normally there are no need to put it in an AreaFix
message but some old AreaFix processors need it in order to work
correctly. If the area manager of the remote system you are currently
configuring needs the tearline in the areafix requests then you must
enable this option, otherwise leave it disabled.
5.5.1.18.11 - Forward changes
FastEcho is capable to automatically forward to your downlinks any
change made in your configuration by a remote system. By enabling this
convenient feature the changes made upon your configured areas (i.e.
area deletion or area renaming) performed by an authorized system using
the the special AreaFix features provided by the two commands
"~<area_tag_to_delete>" and "#<old_area_tag> <new_area_tag>", will be
automatically forwarded to all your downlinks. If the connected systems
are FSC-57 compliants, then the changes made on your system will be
performed automatically on the connected systems too. If the connected
systems aren't FSC-57 compliants but use a normal AreaFix manager, the
modified areas (changed or deleted) will be only disconnected. If your
connected systems are only points-systems they will be noticed for the
changes by mean of a netmail message. If you want to enable the
automatic-forward-changes feature then enable this flag, else leave it
to "No".
5.5.1.19 - Send Notify
This is an AreaFix convenience option. With this switch turned on,
you will be able to send to this node a "NOTIFY" message simply by in-
putting the command "FastEcho Notify" without any parameters from your
DOS prompt. The "NOTIFY" is a particular NetMail message which contains
useful information about the agreements between you and your downlinks
such as: His NetMail and ARCmail addresses, your aka, the AreaFix and
the ARCmail password, the agreed archiver and the ones that you have
available on your system, a brief statistic about received and sent
EchoMails and, last of all, a list containing all active areas for his
node. Sending an AreaFix "NOTIFY" message may be helpful for your down-
link at the first link in order to summarize your agreements. For our
tutorial, switch this option to "Y" status.
───────────────────────────────────────────────────────────────────────
- 57 -
FastEcho MANUAL - Using FastEcho -
───────────────────────────────────────────────────────────────────────
5.5.1.20 - Send Help
Another AreaFix convenience option. By means of this toggle you
will be able to specify to which system you want the function "FastEcho
HELP", when called directly from the DOS prompt, to send the "Area-
Fix.hlp" file (it summarizes all the available AreaFix MetaCommands).
By default this file will be sent by FastEcho to all the systems listed
in "Node Manager". By adjusting this toggle in your configured nodes,
you can filter the FastEcho HELP default behavior, according to your
needs. For our tutorial leave this switch on "Y".
5.5.1.21 - Passive
This option can be switched Y/N both, manually by you, or through
an AreaFix request by this downlink. If a node is switched "Passive" it
will keep all its areas configured and linked but it won't receive any
other mails in areas he is currently linked to (except messages posted
in 'Mandatory' areas). This option could be very useful in order to
temporarily "Suspend" the EchoMail forwarding to nodes that need to
shut down the system for Holidays. In our tutorial leave this option on
"N", of course.
5.5.1.22 - Automatic Passive.
In the Automatic Passive" item you can insert the maximum admitti-
ble number of days that FastEcho has to wait for the downlink calls be-
fore switching it "Passive". In order to preserve your disk-space, you
may activate this option that, automatically, checks if a downlink
isn't calling your system to pick-up its mail for longer than the
number of days specified in this option. If this happens, FastEcho will
switch this system to "passive" status without physically unlinking all
its preconfigured areas. When FastEcho performs this operation it sends
to the "switched" system a NetMail message as notification. This
NetMail message could contain the necessary instruction for this system
in order to become "active" again. This message is fully definible by
you; infact, if FastEcho finds that a text-file named APASSIVE.MSG
(created by you) exists in your system directory, this one will be
brought and used to notify the downlink, if, instead, FastEcho doesn't
find this file, then it will send an hardcoded message automatically.
This function does not work with Binkley-compatible mailers or D'Bridge
if the queue is used. If in your configuration there are more then one
system having the same ARCMAIL address as the one which is switched to
passive status then all these systems are switched to passive too. For
or our tutorial leave this option on "N" status.
5.5.1.24 - 'Node Manager' Function Keys
As introduced, at the beginning of this chapter, there are some
active function keys while you are in "node manager" (view mode). These
keys perform some useful and convenient tasks in a very intuitive way.
Let's now see all these function keys in detail.
───────────────────────────────────────────────────────────────────────
- 58 -
FastEcho MANUAL - Using FastEcho -
───────────────────────────────────────────────────────────────────────
5.5.1.24.1 - Node Manager (Enter key)
We said before that the "node manager" has two main ways of opera-
te: the "view mode" and the "edit mode". When the Node Manager is ac-
cessed, it is automatically switched to "view" mode. In view mode you
can run through all your defined nodes and check their parameters; but
if you need to change something you must switch to "Edit" mode and this
could be done simply by pressing the "Enter" key.
5.5.1.24.2 - Node Manager (F2-Routing)
If you want to change the default NetMail routing for the displayed
node you must press the F2 key while in "Node Manager View Mode". The
following overlapped windows will be shown:
FESetup System Data Export Import F1 Help
░░░░░░░░░░░░░░░░░░░┌─────────────────────┐░░░░░░░░░░░░░░░░░░░░░░░░░░░░
░╔══ 1/1 ═══════════════════ Node-Manager ══════════════════════════╗░
░║ Addresses ║░
░║ Main: 2:999/900.╔═ Route NetMail to ══════╗ 4D/Type 2+: Y ║░
░║ ARCmail: 2:999/900.║ 2:999/900.* ║ TosScan: N ║░
░║ ║ ║ ARCmail 0.60: N ║░
░║ Name: Ben Grimm ║ ║ Pack priority: 0 ║░
░║ ║ ║Convert Umlaut: N ║░
░║ Your Aka: 2:999/999.║ ║ ║░
░║ ║ ║ow Area-Create: N ║░
░║ Passwords ║ ║ Default Group: Y ║░
░║ Packet: ║ ║Export By Name: N ║░
░║ AreaFix: THETHING ║ ║ ║░
░║ Status ║ ║ AreaFix flags: » ║░
░║ ARCmail: None ║ ║ ║░
░║ AreaFix: None ║ ║ Send Notify: Y ║░
░║ Packer: ZIP Max║ ║ Send Help: Y ║░
░║ ║ ║ ║░
░║ Groups: AB ║ ║ Passive: N ║░
░║ Security: 100 ╚═════════ via this node ═╝matic Passive:0 ║░
░║ ║░
░╚══════════════════════════════════════════════════════════════════╝░
░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
Enter-Edit Ins-Add Del-Delete F2-Rout F5-Browse F4 Area List F5-Copy
But what's the NetMail routing?. The routing represents the path
that the NetMail messages, created or in transit upon your system, must
follow to reach the destination. The case shown in the picture, means
that you want to route all NetMail messages addressed to the 2:999/900
points (that's the node shown in the node manager screen) via the
2:999/900 system. That's the default routing suggested by FastEcho di-
rectly. You can, obviously, perform any different choices according to
your needs. Specifing the NetMail routing you can rely on special sym-
bols called "wildcard", the symbol "*" asterisk will take into conside-
ration all possible addresses after the ones specified (see the
ROUTE.FE chapter for further information routing statements). The sta-
tement shown in pictures, will obtain the routing of all NetMails for
the node 2:999/900 and all its points (I.E. 2:999/900.1, 2:999/900.2
and so on) through the same 2:999/900 node. If, instead, you want
route, through the node 2:999/900 all NetMail messages for the zone
"2", then you must delete the actual default routing statement
───────────────────────────────────────────────────────────────────────
- 59 -
FastEcho MANUAL - Using FastEcho -
───────────────────────────────────────────────────────────────────────
"2:999/900.*" replacing it with "2:*". The NetMail routing you will
define here will always be relative to the node shown in the benehat
screen of the "node manager". As you can see, this option is somewhat
complex but it's really powerful; you can define in the box shown up to
15 different routing-statements but remember that valid statements must
always be defined in the standard "Zone:Net/Node.Point" format,
further, each statement can be shortened with the aforesaid wildcard
"*" or the "ALL" verb. the NetMail routing defined here has its own
"top-down" hierarchical priorities over five levels:
Zone:Net/Node.Point Level 4
Zone:Net/Node.* Level 3
Zone:Net/* Level 2
Zone:* Level 1
* Level 0
The higher this level will be, the higher priority the routing
statement will have. For example, if you have 3 nodes: Node "A", Node
"B" and Node "C" defined in your Node-Manager. Node "A" has "2:*" as
routing statement, Node "B" has "2:999/*" and Node "C" has only "*" in
its "route NetMails to" box. Now you send a NetMail for the point
2:999/904.9. Through what system will FastEcho route it? It will be
routed through the "B" system, of course, that's because it has a rou-
ting level of "2" which is higher than system "A" which has a routing
level of "1" and higher than system "C" too, because this one has one
routing level of "0" which is hierarchically the last.
5.5.1.24.3 - Node Manager (F3-Browse)
This is a shortcut key to select the node you need in a very prati-
cal way, without running through all "node-manager" records but simply
selecting it by means of a nice popup window. When you are in "view"
mode, by pressing the "F3" key, the following window will be shown to
you, superimposed at your main "node manager" layout:
FESetup System Data Expo┌──────────────────────────────────┐
░░░░░░░░░░░░░░░░░░░┌─────────────│>2:999/900.0 [Ben Grimm]<│░
░╔══ 1/1 ═══════════════════ Node│ 16:999/900.0 [Sue Wright] │░
░║ Addresses │ 2:999/999.1 [Franklin Richards] │░
░║ Main: 2:999/900.0 └──────────────────────────────────┘░
░║ ARCmail: 2:999/900.0 ARCmail 0.60: N ║░
░║ Pack priority: 0 ║░
░║ Name: Ben Grimm ║░
To select a different node, simply move the highlighted box, with
the arrows-keys, on the one you need and then press "return". Im-
mediately your requested node will be shown in the "node manager" main
screen. If you have followed the tutorial until now, you will see in
this window only the node you have already defined: the 2:999/900. You
will be able to see the other as soon as you define them.
───────────────────────────────────────────────────────────────────────
- 60 -
FastEcho MANUAL - Using FastEcho -
───────────────────────────────────────────────────────────────────────
5.5.1.24.4 - Node Manager (F4-Area List)
This shortcut key can really save you a lot of time! When you are
in the main "node-manager" window, simply by pressing the "F4" key, a
new window will overlap the present one. Look at the picture below:
FESetup System Data Export Import ┌────────────────────┐
░░░░░░░░░░░░░░░░░░░┌─────────────────────┐░░░░░░│ ■ CLIPPER │
░╔══ 1/1 ═══════════════════ Node-Manager ══════│ ■ CLANG │
░║ Addresses │ DEWDNEY │
░║ Main: 2:999/900.0 │ ■ SF │
░║ ARCmail: 2:999/900.0 │ ■ SysOp_CHATTER │
░║ │ ■ SysOp_COORD │
░║ Name: Ben Grimm └────────────────────┘
The new window, visible at the right side of your screen, lists al-
phabetically all the areas accessible by this node, both linked or not.
This gives you a direct overview of all areas available to it according
to its available groups (see: 5.5.1.8) and to its security level (see:
5.5.1.9); You can link or unlink areas for this node simply by moving
the highlighted box on the areas you want and tagging them by way of
the "space-bar" key. When an area is linked, a small black box will be
visible to the left of the area-name. Here you always have the "Speed-
Search" function available: To search an area in the list, simply start
fingering its name on your keyboard, immediately the cursor will be
placed upon the area you need (if available). When you have finished
tagging or untagging the area-names you want, then FastEcho will do,
for you, all the necessary adjustments in Area-Manager automatically.
In our tutorial we shall see nothing in this box, that's normal,because
we haven't yet defined any areas in "area manager" section.
5.5.1.24.5 - Node Manager (F5-Copy)
By means of this useful option you will be able to "replicate" an
existing node (already defined), duplicating any of its entry; further-
more, you can modify the duplicated record according to your needs.
This feature can be very helpful when you have to define in "node
manager" several nodes which have similar characteristics by changing
only the different ones (I.E. net address or some advanced options).
This may let save you lot of time when configuring FastEcho.
5.5.1.24.6 - Node Manager (Ins-New Entry)
This key is only useful if you want to insert a new system in your
"Node Manager" database. When you strike the Ins key a new empty entry
form (see:5.5.1) will be shown to you, ready to be dressed with new
data, in order to define a new uplink or downlink.
───────────────────────────────────────────────────────────────────────
- 61 -
FastEcho MANUAL - Using FastEcho -
───────────────────────────────────────────────────────────────────────
5.5.1.24.7 - Node Manager (Del-Delete)
This is only useful if you want to remove a node from your FastEcho
configuration. When you are in "Node Manager" "View" mode, by pressing
the "Del" key, the currently selected system will be marked for dele-
tion. Infact, it won't be removed immediately, but, at the top of your
screen, near the record number, the label "Deleted" will be clearly
shown. The physical removal of the system marked for deletion will hap-
pen, after confirmation, when you leave the "node manager".
.-.-.
Here you have finished the dressing of your first system in "Node
manager". Now you have the right information to complete it by defining
the other two systems: the 16:999/999 and the 2:999/999.1. Repeat the
step already seen from 5.5.1 to 5.5.1.23 until you have finished. When
done press the "ESC" key to return back into the "Data DropDown Menu".
5.5.2 - Group Area Defaults
This is one of the most powerful capabilities of FastEcho: The area
grouping. Through this section it is possible to setup every group with
your customized predefined values that will reflect the group needs.
For example you may define a group for your local areas, another for
your national FidoNet areas, another for international FidoNet areas
and as many groups as many net you are involved in, every group with
its specific defaults. We have already defined the group-names (see:
5.4.13) now we must define the groups peculiarity, so, these group-
names will be re-proposed as group titles. The groups will be used
several times in many FastEcho tasks. The first we shall see is their
use in Area-Definition: When you define a new area you will be prompted
to select to what group the area you are defining will belong to, and,
after you have choosen it, you will be asked if FESetup shall take over
the selected groups defaults or not. Another task where FastEcho takes
advantage of the use of group structures is when it performs an "Auto-
Area-Create" operation (we have already met Auto-Area-Create: see
5.5.1.15 and 5.4.7.3 chapters) I.E. You can specify to which kind of
group the newly created area will belong to (Local/EchoMail), define
the type of storage, preset the flags and automatically forward the
new area to the systems listed in 'Export-to', this reduces the
need of manual inter-action to a minimum. Another useful Group
application is the capability to perform Global changes on several
areas simply selecting them by groups. but we shall see this option
later in the manual. Now place the Highlighted box on "Group Area
Defaults" item and strike "return". You will see the following screen:
FESetup System Data Export Im┌───────────────────────────────┐
░░░░░░░░░░░░░┌─────────────────────┐░│>A) - FidoNet EchoMail Natl< │
░░░░░░░░░░░░░│ Node-Configuration │░│ B) - FidoNet EchoMail Intl │
░░░░░░░░░░░░░│>Group Area Defaults<│░│ C) - ZyXELnet EchoMail Area │
░░░░░░░░░░░░░│ Area-Configuration │░│ D) - Local BBS Area │
░░░░░░░░░░░░░│ Carbon Copies │░│ E) │
░░░░░░░░░░░░░│ AreaFix Options │░│ F) │
░░░░░░░░░░░░░└─────────────────────┘░│ G) │
░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░│ [...] │
░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░│ V) │
░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░│ W) │
Edit area defaults for each group └───────────────────────────────┘
───────────────────────────────────────────────────────────────────────
- 62 -
FastEcho MANUAL - Tutorial - Data dropdown menu - Group area Defaults -
───────────────────────────────────────────────────────────────────────
As you can immediately see, the group names contained in the box to
the right of your screen are the same that you defined in "Group Names"
section (See: 5.4.13). Now you should fix the default values for each
of them. To do so, place the highlighted box upon the (group "A") group
and strike return. You will obtain the following layout:
FESetup System Data Export Import F1 Help
╔═════════════════════ Area defaults for Group A ════════════════════╗
║ Comment: FidoNet EchoMail Natl ║
║ Origin: System in test @Fidonet.org ║
║ Type: EchoMail ║
║ Storage: Hudson Board: 1 ║
║ Path: ║
║ Use Aka: 2:999/999.0 ║
║ ║
║ Mandatory: N Keep SEEN-BY: Y Tiny SEEN-BY: N CPD: N ║
║ Convert Umlaut: N Keep users: N Kill read: N Disab. Psve: N ║
║ Remote changes: Y Hide area: N Keep NetMail: N ║
║ ║
║ Purging # Msgs: 50 # Days: 30 # Rcvd Days: 0 ║
║ Security Read: 0 Write: 0 ║
║ ║
║ SEEN-BY: 2:999/999.0 ║
║ Export to: 2:999/900 ║
╚════════════════════════════════════════════════════════════════════╝
Press F10 to save or ESC to abort editing...
Now we'll begin the dressing of the area default for group "A". no-
tice that your screen, now, won't look exactly like the one in this
picture because you havent yet inserted any data.
5.5.2.1 - Comment (default)
In this field you may enter the default description that will be
initially assigned, in area manager, to each area when you confirm to
take over the selected group default; then you may modify this defaul-
ted description according to your needs.
5.5.2.2 - Origin (default)
When the cursor will fall into the "Origin" item, the following
box will popup automatically:
FESetup System Data Export Import F1 Help
╔═══════════════════════ Area defaults for Group A ══════════════════╗
║ Comment:┌───────────────────────────────────────────────────────┐ ║
║ Origin:│>A) This is the Reed's system< │ ║
║ Type:│ B) System in test@Fidonet.org │ ║
║ Storage:│ C) System in test@ZyXELNET.ftn │ ║
║ Path:│ D) │ ║
║ Use Aka:│ E) │ ║
║ │ [...] │ ║
╚═════════│ T) │══╝
░░░░░░░░░░│ U) (Empty) │░░░
Press F10 └───────────────────────────────────────────────────────┘
───────────────────────────────────────────────────────────────────────
- 63 -
FastEcho MANUAL - Tutorial - Data dropdown menu - Group area Defaults -
───────────────────────────────────────────────────────────────────────
We have already extensively talked about "Origin" lines and their
means, previously in this manual (see: 5.4.14 chapter) when we defined
them. Now it's time to begin using these defined origin-lines assigning
them to one or more "group area defaults" record. The box appeared
overlying the main "Area Defaults" screen assignment, contains the
exact origin lines you defined in the 5.4.14 chapter. Here you cannot
modify their contents, you may only select the one that fits the group
area requirements. To select your preferred origin line, you must move
the highlighted box, by means of your arrows-key, placing it upon the
origin line you need and then confirming your choice pressing, the
"Return" key. When finished, you will see only your selected "origin"
line displayed in the "Area Defaults" screen assignment. For our tuto-
rial, place the cursor upon the "B" Item (System in Test@Fidonet.org)
and press return.
5.5.2.3 - Type (default)
Here you must define the type of area (EchoMail, NetMail, Local)
for this specific group. When the cursor falls in the "type" item, you
will be prompted to select your preferred one by means of the following
popup selector:
FESetup System Data Export Import F1 Help
╔═════════════════════ Area defaults for Group A ════════════════════╗
║ Comment: FidoNet EchoMail Natl ║
║ Origin: System in test @Fidonet.org ║
║ Type: ┌─────────────┐ ║
║ Storage: │>EchoMail< │ Board: 1 ║
║ Path: │ NetMail │ ║
║ Use Aka: │ Local │ ║
║ │ BadMail │ ║
║ Man│ DupeMail │SEEN-BY: Y Tiny SEEN-BY: N CPD: N ║
║ Convert └─────────────┘p users: N Kill read: N Disab. Psve: N ║
║ Remote changes: Y Hide area: N Keep NetMails: N ║
[...] [...]
╚════════════════════════════════════════════════════════════════════╝
Press F10 to save or ESC to abort editing...
We have already pointed out the main differences between EchoMail,
NetMail and Local areas (see: 5.4.14.1) but here we can see another two
different area types: "BadMail" and "DupeMail". we'll see later that
one "BadMail" area needs to be defined (it's mandatory) otherwise
FastEcho may not work properly, while the "DupeMail" area may be defi-
ned in order to enable the FastEcho's dupechecking feature. Make sure
to make your right choice here by selecting the proper area "type" in
accordance with this group's target. To select a "type" simply move, as
usual, the box over the item you need and strike return to confirm;
doing so you will see your choice displayed on the "Group Area Default"
main layout. For our tutorial select the "EchoMail" area type and
press return to continue.
───────────────────────────────────────────────────────────────────────
- 64 -
FastEcho MANUAL - Tutorial - Data dropdown menu - Group area Defaults -
───────────────────────────────────────────────────────────────────────
5.5.2.4 - Storage (default)
In the previous item we defined the type of area for this group;
In this one you must define, instead, your preferred storage standards.
FESetup System Data Export Import F1 Help
╔═════════════════════ Area defaults for Group A ════════════════════╗
║ Comment: FidoNet EchoMail Natl ║
║ Origin: System in test @Fidonet.org ║
║ Type: EchoMail ║
║ Storage: ┌─────────────┐ Board: 1 ║
║ Path: │>Hudson< │ ║
║ Use Aka: │ Fido *.MSG │ ║
║ │ Squish │ ║
║ Man│ JAM │SEEN-BY: Y Tiny SEEN-BY: N CPD: N ║
║ Convert │ Passthrough │p users: N Kill read: N Disab. Psve: N ║
[...]mote c└─────────────┘de area: N Keep NetMail: N [...]
╚════════════════════════════════════════════════════════════════════╝
Press F10 to save or ESC to abort editing...
FastEcho can store messages with several storage standards (HMB,
JAM, SQUISH, MSG) and each of them has its specific proprieties, advan-
tages and disadvantages. Your possible choice may fall upon one storage
type instead of another because it's the one that your BBS system sup-
ports or because of your personal preferences. The Hudson Message Base
(aka QBBSbase) is the fastest storage type up until now but it has
some major limitations in maximum number of available boards (up to
200) and in maximum number of messages in all the defined boards (up to
16000); Fido *.MSG, Squish and Jam messagebases don't suffer this
limitation but they are a lot slower in processing: this is due to
their specific characteristics and structures. For our tutorial select
in this window the "Hudson" storage type and strike "return" key.
5.5.2.5 - Board (default)
This setting is only used in "Hudson" storage type; if you, in the
previous option, have selected a storage type different from the "Hud-
son" one, then you won't be able to access this item. On the countrary,
if you selected "Hudson", the cursor will be positioned herein waiting
for a number by you. When you complete this "Group Area Default"
section, you will need to add the areas in "Area Manager" and, there,
FastEcho will ask you if it has to take over the default you assigned
here, so, when you confirm to take over this "group default" while
adding a new board in "Area Manager" or when FastEcho performs an "Auto
Area Create" operation, this default board number will instruct
FastEcho to scan the free Hudson board starting from the number
specified, until it reaches the board 200. If FastEcho is unable to
find any free board starting from the specified one, then the messages
will be tossed in the "BadMail" board. For our tutorial, input here
the number "1" and strike the "return" key to continue.
5.5.2.6 - Path (default)
This item will be accessible only if you specified a "Storage" type
different from "Hudson". The main difference between the "Hudson" sto-
rage type and the other (JAM, SQUISH and MSG) is that while the "Hud-
son" storage type handles all the boards you can define (max. 200) into
───────────────────────────────────────────────────────────────────────
- 65 -
FastEcho MANUAL - Tutorial - Data dropdown menu - Group area Defaults -
───────────────────────────────────────────────────────────────────────
some files located in a single directory that you have already defined
(See: 5.4.4 - PathNames and 5.4.4.2 - Messagebase), the JAM, SQUISH
ones need to be defined area by area in different files because of
their structures. The specified path will be used as base path were for
JAM and Squish the new area files will be created and for *.MSG a new
directory will be created when Auto-Area-Create is actived.
5.5.2.7 - Use Aka (default)
Here you may define your default aka (address) for the areas be-
longing to this group. When you place the cursor upon this field, you
will see the following box:
┌───────────────┐
Use Aka: │>2:999/999< │
│ 16:999/999 │
└───────────────┘
Your aka must be chosen in accordance with the uplink address who
you call for this group of areas. For example, if your FidoNet uplink
address is the 2:999/900 and you are defining the "Fidonet EchoMail
group" then, if your FidoNet aka for this uplink is 2:999/999, you must
insert it in this field. For our tutorial, place the highlighted box
upon the "2:999/999" aka and strike the "return" key to continue.
5.5.2.8 - Others "Group Area Defaults" switches
All the other "Group area Default" switches that you can see in the
this "Group area Default" layout (Mandatory, Keep SEEN-BY, Tiny SEEN-
BY, CPD, Convert Umlaut, Keep users, Kill read, Disable Passive, Remote
changes, Hide area, Keep NetMails, Purging Msgs, Days, Rcvd Days, Secu-
rity Read, Write) have exactly the same meanings as the ones you will
see in the "Area definition" layout. In order to avoid explaining them
over and over again, I willingly omit them. Take, as datum-point, the
same options you will see in aforesaid layout, and then, you will come
back here to follow the explanation. Keep in mind that the ones you
will define in the present section will be defaulted to all the areas
that belong to the specified group. Once the default group's values are
assigned to a particular area, these values may of course be changed by
you according to your needs. For our tutorial now skip to the
5.5.3.1.10 chapter to continue and, when signaled, return back here to
the 5.5.2.9 chapter.
5.5.2.9 SEEN-BY (default)
It will be more convenient for you to define the "SEEN-BY" and the
"Export-To" items in the "default" section for each group, instead of
specifing them repeatedly while defining each single area. Here you
will define the "SEEN-BY" item. Place the cursor upon the SEEN-BY item
and strike the return key. You will see the following box:
┌─────────────────┐
SEEN-BY:│■ >2:999/999< │
Export to:│ 16:999/999 │
└─────────────────┘
───────────────────────────────────────────────────────────────────────
- 66 -
FastEcho MANUAL - Tutorial - Data dropdown menu - Group area Defaults -
───────────────────────────────────────────────────────────────────────
But What is the "SEEN-BY"? It can be considered as an EchoMail
tool. At the bottom of each EchoMail message may exist an item marked
as "SEEN-BY" immediately followed by as many net addresses as many sys-
tems have already seen. These are necessary for mail processing.
Its presence can be useful only on multiline systems to avoid
problems with the detection of the dupes (EchoMail messages erroneously
duplicated) or for route-debugging purposes. Obviously you must select
the right Seen-by that reflects your aka for this particular group; for
example, if you are defining the group for your FidoNet EchoMail areas
that you pick up from the uplink with 2:999/900 as net address and you
have two akas: "2:999/999" and "16:999/999", then your SEEN-BY for this
uplink will be, very likely, the "2:999/999" one; (it usually matches
the. "Use AkA" setting that we saw above in 2.2.5.7 paragraph) but if
you have a multiline system with more that one Fidonet aka you may
select more than one SEEN-BY too, inspite of your "use Aka" setting. To
select the SEEN-BY you want, you must, as usual, move the highlighted
box upon the right address and press the "space bar" until you have
marked all the SEEN-BY items you wish (you will see one small black box
to the left of each selected SEEN-BY) and, then, press the return key
to confirm your selections. For our tutorial select the "2:999/999" as
SEEN-BY address.
5.5.2.10 - Export-To (default)
Any EchoMail area that you receive from your uplink may be
exported to your downlinks. FastEcho, of course, to correctly perform
this task, needs to be informed to whom downlinks you want export mail
and which areas it has to export So now, you know that "somewhere" you
must specify the areas to export and the net-address of the system to
whom you want FastEcho to export them. Keep in mind that in this
section we are only defining the "group-defaults"; so place the cursor
over the "Export-To" item and strike the "Return" Key. You will see the
following window:
FESetup System Data Export Impor┌─────────────────────────┐
╔═════════════════════ Area defaults for Gr│ ■ 2:999/900.0 │
║ Comment: FidoNet EchoMail Natl │ 2:999/999.1 │
║ Origin: System in test @Fidonet.org │ 16:999/999.0 │
║ Type: EchoMail │ │
[...] [...] [...]
║ SEEN-BY: 2:999/999.0 │ │
║ Export to: 2:999/900 │ │
╚══════════════════════════════════════════└─────────────────────────┘
Press F10 to save or ESC to abort editing
In the present item we might define the downlinks that want to re-
ceive this particular group of areas so you will attain two main tar-
gets: Firstly you will find your downlinks already defined when you
setup your areas belonging to this group, avoiding to reselect them
every time, and, further, you will be able to rely on the "Auto-Area-
Create" autoforward feature. What's this!?!?. Very simple. We have met
the "Auto-Area-Create" feature several times in this manual (see:
5.5.1.15, 5.4.7.3, 5.4.7.4 and 5.4.7.5 chapters) and you now already
know that by means of this function you could obtain that FastEcho per-
forms several automated operations in order to add a new area in its
configuration, in your Mailer and in your BBS configurations. If you
specify your downlinks in this default "Export-to" setting, then every
───────────────────────────────────────────────────────────────────────
- 67 -
FastEcho MANUAL - Tutorial - Data dropdown menu - Group area Defaults -
───────────────────────────────────────────────────────────────────────
new area that FastEcho will add automatically will also be directly
forwarded to your downlinks, that you have specified in this field,
without any of your manual intervention. For our tutorial place the
highlighted box upon the 2:999/999 address which is the right one, mark
it by pressing the "space bar" and then strike return to confirm.
.-.-.
Here you have finished the setup of your first "Group Area De-
fault"; you must now setup the other two groups: one for the "Fidonet
EchoMail Intl": the Fidonet international area , and one for "ZyXELnet
EchoMail"; repeat the steps from 5.5.2 toward 5.5.2.10 until you have
finished;then press the "ESC" key to return to the "Data Dropdown Menu"
5.5.3 - Area Configuration
------------------
In this section you will define and setup every EchoMail, NetMail,
Local and Special areas you will use in your daily activities. We have
already talked about EchoMail and NetMail differences several times
(see: 5.5.2.3, 5.4.14.1, 5.4.14.1.1 and 5.4.14.1.2) so, I assume that
you have acquired a good knowledge of them; but there are two more area
types that we haven't mentioned so much: The "Local" and the "Special"
areas. The "Local" are areas that will never be forwarded to other
systems and will never be picked up from other systems by you. The mes-
sages contained in local areas are, so, locally created in your system
and locally read too (for example the local areas of your BBS); they
are somewhat useless for point systems, with the only exception that
they may be used for "Carbon Copy" (see the introduction to the 5.5
chapter) we'll see better the means of the "Carbon Copies" function and
its use in "Using FastEcho" later in this manual. The "Special" is, in-
stead, a kind of area that FastEcho needs in order to perform two main
operations: The first is detecting all bad messages that don't match
your preferences settled in FESetup, and the second is intercepting all
incoming duplicated messages (better known as "dupes"). The first
special area, that's mandatory, is the "BadMail" area and the second
one is the "DupeMail" area respectively. Keep in mind to define these
two important areas because, otherwise, FastEcho will not work pro-
perly. From the "Data DropDown Menu" Place the highlighted box upon the
"Area Configuration" item and strike the return key. You will see the
following screen:
FESetup System Data Export Import F1 Help
░░░░░░░░░░░░░░░░░░░░░░┌─────────────────────┐░░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░░░░░░░░░░│ Node-Configuration │░░░░░░░░░░░░░░░░░░░░░░░░
╔══ 1/0 ════════════════════ Area-Manager ══════════════════════════╗
║ Brd Area Name Used Aka Grp ║
║───────────────────────────────────────────────────────────────────║
║ ║
[...] [...]
║ ║
╚═══════════════════════════════════════════════════════════════════╝
░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
Enter-Edit Ins-Add Del-Delete F2-Sort F3-Tag F4 Srch F5-Copy F6-Glbal
───────────────────────────────────────────────────────────────────────
- 68 -
FastEcho MANUAL - Tutorial - Data dropdown menu - Area Configuration -
───────────────────────────────────────────────────────────────────────
The one you are looking at now is the area browser, it's subdivided
into four columns: Brd -> That identifies the number of boards belong-
ing to the HMB or the type of messagebase you will use for the listed
area (F) for FidoNet *.MSG areas, (S) for Squish areas and (J) for JAM
area, the Name (TAG) of the area, the AKA that you have choosen for the
listed area and, finally, the belonging group. Naturally, in this mo-
ment the window is empty because we haven't yet defined any area,but we
shall start soon. Let's go to the first area pressing the Ins key.
5.5.3.1 - The Area definition layout
After you have pressed the "Ins" key, the following layout will be
shown on your display:
╔═════════════════════════════ Edit Area ════════════════════════════╗
║ Name: Group: ║
║ Comment: ║
║ Origin: ║
║ Type: EchoMail ║
║ Storage: Hudson Board: ║
║ Path: ║
║ Use Aka: ║
║ ║
║ Mandatory: N Keep SEEN-BY: N Tiny SEEN-BY: N CPD: N Psive: N ║
║ Convert Umlaut: N Keep users: N Kill read: N Disble Psive: N ║
║ Remote changes: Y Hide area: N Keep NetMail: N ║
║ ║
║ Purging # Msgs: 0 # Days: 0 # Rcvd Days: 0 ║
║ Security Read: 0 Write: 0 ║
║ ║
║ SEEN-BY: ║
║ Export to: ║
║────────────────────────────────────────────────────────────────────║
║Press F10 to save or ESC to abort editing... ║
╚════════════════════════════════════════════════════════════════════╝
Here you must define all the parameters needed to correctly handle
each of your areas. When you start defininig your area, the cursor
will be placed automatically upon the "Name" Item.
5.5.3.1.1 - Name
Each EchoMail area has an unique name also known as area tag. In
this Item the name of the areas you are defining must be correctly
inserted. Make sure to insert this tag correctly otherwise you will not
be able to send nor receive anything in this area. There are official
documents which report and describe each area, each with its topic and
its area tag, these documents are the so called "echolist". At the
beginning you can ask your uplink for the available areas too and then
ask for the "echolist". For our tutorial we shall input there one fake
name "TESTECHO1" but, after we have finished, make sure to change this
one with the right one that you wish to import from your uplink.
───────────────────────────────────────────────────────────────────────
- 69 -
FastEcho MANUAL - Tutorial - Data dropdown menu - Area Configuration -
───────────────────────────────────────────────────────────────────────
5.5.3.1.2 - Group
When the cursor falls into the "Group" item, the following screen
will be presented to you:
╔═════════════════════════════ Edit A┌───────────────────────────────┐
║ Name: TESTECHO1 │>A) Fidonet EchoMail Natl< │
║ Comment: │ B) Fidonet EchoMail Intl │
║ Origin: System in test @Fidonet.or│ C) ZyXELnet EchoMail Area │
║ Type: EchoMail │ D) Local BBS Area │
║ Storage: Hudson Board:1 │ E) │
║ Path: │ F) │
║ Use Aka: 2:999/999.0 │ G) │
[...] [...] [...]
║ │ X) │
║────────────────────────────────────│ Y) │
║Press F10 to save or ESC to abort ed│ Z) │
╚════════════════════════════════════└───────────────────────────────┘
You may note that the groups in the windows are the same that we
defined in "Group-Area-Default" (see: 5.5.2). All that you have to do
is select the right group to which this area will belong to, supposing
that the one we are defining is a National FidoNet EchoMail area, then
we shall select the "B" group that perfectly fits our needs because
it's the International FidoNet EchoMail Group. For our tutorial, place
the highlighted box over the "A" group and strike return, immediately
we shall see the following box:
╔═════════════════════════╗
║ ║
║ Take over new group's ║
║ defaults ? (Y,N) ║
║ ║
╚═════════════════════════╝
If you accept, by pressing the "Y" key, the previously defined de-
fault values of the selected group will be copied into your new area.
If you deny, by pressing the "N" key, you will have to modify all items
according to your needs manually.
For our tutorial, we shall press the "Y" key.
5.5.3.1.3 - Comment
In this field you can input the description of the area you are
defining or its purpose too. This description will be, also, used to
document the area listing generated by FastEcho-AreaFix when your down-
links forward you an AreaFix request containing the %LIST MetaCommand.
To let FastEcho-AreaFix produce this descriptive list, you have to ena-
ble the "Detailed List" item switching it to "Y". (You can find the
"Detailed List" toggle in the "AreaFix option" item of the "Data Drop-
down menu" but we shall meet this in the 5.5.6.9 chapter, later in this
manual). For our tutorial input in this field "Exemplifying Board" and
strike return to continue.
───────────────────────────────────────────────────────────────────────
- 70 -
FastEcho MANUAL - Tutorial - Data dropdown menu - Area Configuration -
───────────────────────────────────────────────────────────────────────
5.5.3.1.4 - Origin
After you have inserted your preferred area description relative to
the area you are defining in the "Comment" item, you will immediately
be prompted to select the proper "Origin" line for this area by means
of the following box:
╔═════════════════════════════ Edit Area ════════════════════════════╗
║ Name: TESTECHO1 Group:A ║
║ Comment: Exemplifying Board ║
║ Origin:┌────────────────────────────────────────────────────────┐ ║
║ Type:│>A) This is the Reed's system< │ ║
║ Storage:│ B) System in test@Fidonet.org │ ║
║ Path:│ C) System in test@ZyXELNET.ftn │ ║
║ Use Aka:│ D) │ ║
[...] [...] [...]
║─────────│ T) │─║
║Press F10│ U) (Empty) │ ║
╚═════════└────────────────────────────────────────────────────────┘═╝
We have already talked about origin lines several times in this
manual (see: 5.5.2.2, 5.4.14, 5.4.14.1 and 5.4.14.2).Remember that the
one you define now, will be taken to be inserted in your EchoMail mes-
sages that you, or the user of your BBS system, will insert in this
area. Naturally here you must select the right "Origin" line, accor-
ding to the net which this area belongs to, or, if you have defined
more that one origin for the same net, you may define your preferred
one. FastEcho will of course only add an Origin line to exported
messages when your editor didn't add one when writing the mail. For our
tutorial place the highlighed box over the "origin" tagged as "B" and
strike the "return" key to continue.
5.5.3.1.5 - Type
When the cursor has passed over the "Type" item you will be imme-
diately prompted to select the area type. FastEcho will show you the
following popup-box to let you choose the right one:
╔═════════════════════════════ Edit Area ════════════════════════════╗
║ Name: TESTECHO1 Group:A ║
║ Comment: Exemplifying Board ║
║ Origin: ┌───────────┐ ║
║ Type: │>EchoMail< │ ║
║ Storage: │ NetMail │ Board: ║
║ Path: │ Local │ ║
║ Use Aka: │ BadMail │ ║
║ │ DupeMail │ ║
║ Mand└───────────┘ SEEN-BY: N Tiny SEEN-BY: N CPD: N Psive: N ║
[...] [...]
║────────────────────────────────────────────────────────────────────║
║Press F10 to save or ESC to abort editing... ║
╚════════════════════════════════════════════════════════════════════╝
Here you must select the type of area you are defining, as you cer-
tainly already know, these types will be treated in a very different
way: The EchoMail areas must contain all public messages that will be
───────────────────────────────────────────────────────────────────────
- 71 -
FastEcho MANUAL - Tutorial - Data dropdown menu - Area Configuration -
───────────────────────────────────────────────────────────────────────
exported/imported in the normal way to/from your downlinks/uplinks, The
NetMail areas must contain only private messages having one unique
sender address and one unique receiver address (in particular, the Net-
Mail areas you will define here will be called "Secondary NetMail
Area"; don't confuse the "Secondary" with the "Primary" NetMail area
(to see the differeces between them please read paragraph 5.4.4.1). The
"Local" areas must contain only messages for local use (I.E. the mes-
sages exchanged between your BBS users or messages copied by "FastEcho
Carbon Copy" Function. The BadMail area is the only MANDATORY area
that MUST exist in your FESetup area definition; FastEcho needs this
area in order to correctly handle all the messages that don't match
your FESetup specifications when it tosses the incoming mail packets
coming from your uplinks/downlinks. The DupeMail area is an area that
may be defined if you want to enable the FastEcho power to detect the
erraneously duplicated messages, contained in mail packets, coming from
your uplinks/downlinks. If you still aren't sure about the existing
differeces between the NetMail, EchoMail, Local, BadMail and DupeMail
please read carefully through the following chapters: 5.4.14.1.1,
5.4.14.1.2 and 5.5.3 before you run the risk of selecting a wrong area
type. For our tutorial, place the highlighted box over the "EchoMail"
item and strike the return key to follow up.
5.5.3.1.6 - Storage
Immediately after the definition of the "Type" of area, FESetup
will ask you what kind of storage you need for the area you are defi-
ning. You may choose between Hudson, JAM, Squish and Old-Fido-style
*.MSG storage methods. The dialog box that FESetup will show you will
be the following:
╔═════════════════════════════ Edit Area ════════════════════════════╗
║ Name: TESTECHO1 Group:A ║
║ Comment: Exemplifying Board ║
║ Origin: System in test@Fidonet.org ║
║ Type:┌─────────────┐ ║
║ Storage:│>Hudson< │ Board: ║
║ Path:│ Fido *.MSG │ ║
║ Use Aka:│ Squish │ ║
║ │ JAM │ ║
║ Man│ Passthrough │SEEN-BY: N Tiny SEEN-BY: N CPD: N Psive: N ║
[...] └─────────────┘ [...]
║────────────────────────────────────────────────────────────────────║
║Press F10 to save or ESC to abort editing... ║
╚════════════════════════════════════════════════════════════════════╝
The storage methods that you will select in this box are better
known as "messagebase type". Each of these messagebases has its pecu-
liar charachteristic. We shall point out the main two: The Hudson is
the quickest message base you can find up until now, but it has two
main limitations in the maximum number of messages that it can hold
(16000) and the maximum number of definable boards (200); all the
messages in all boards will be gathered together into 5 files located
in one unique directory (the one you defined in the 5.4.4. chapter at
the "Messagebase" item).The files, belonging to the Hudson base, that
FastEcho could create automatically are: MSGHDR.BBS, MSGIDX.BBS,
MSGTXT.BBS, MSGTOIDX.BBS, MSGINFO.BBS. The JAM and SQUISH messagebase
types, instead, needs to have every area in a separate file and, if
───────────────────────────────────────────────────────────────────────
- 72 -
FastEcho MANUAL - Tutorial - Data dropdown menu - Area Configuration -
───────────────────────────────────────────────────────────────────────
you want, in a separate directory too. The Fido (*.MSG) messagebase
needs to have every area in separate directories only. If you choose
to use one JAM, SQUISH or *.MSG messagebase FESetup will later ask you
the pathname for the area you are defining; which is not necesary for
the Hudson message base where you must only select the board without
pathname. The last Item shown in the dialog box is relative to the
"Passthrough" status: this is not a kind of messagebase; selecting this
one means that you aren't interested to it but you import it, all the
same, for the benefit of your downlinks who need it; thus, if you mark
some areas as "Passthrough" neither you nor your interactive-BBS-users
will be able to read it. For our tutorial place the Highlighted box
over the "Hudson" storage type and strike "return".
5.5.3.1.7 - Board
This setting will be accessed only if you, in the previous item,
have choosen the "Hudson" storage type; if you, in the previous option,
have selected a storage type different from the "Hudson" one, then you
won't be able to access it. As said before in several occasions, the
Hudson messagebase can hold up to 200 boards. This number represent the
number of board you want to assign to the present area. Naturally it
will be automatically ranged from 1 to 200. For our tutorial leave
FESetup to choose the right board for you and strike the "return" key
to continue.
5.5.3.1-8 - Path
This item, in opposition with the precedent one, will be accessible
only if you have specified a "Storage" type different from "Hudson". As
previously said, the SQUISH, JAM and *.MSG messagebases needs to have
their areas stored in seperate files. For SQUISH and JAM you could
leave more than one area in the same directory but each file must have
a different name, as for the *.MSG messagebase,every area must reside
in different directories. Here you must specify the pathname different
to the area you are defining.
5.5.3.1.9 - Use Aka
When the cursor will transit over the "Use Aka" item, you will im-
mediately see the following dialog-box popping up on your screen.
╔═════════════════════════════ Edit Area ════════════════════════════╗
║ Name: TESTECHO1 Group:A ║
║ Comment: Exemplifying Board ║
║ Origin: System in test@Fidonet.org ║
║ Type: EchoMail ║
║ Storage: Hudson Board: 1 ║
║ Path:┌───────────────┐ ║
║ Use Aka:│>2:999/999.0< │ ║
║ │ 16:999/999.0 │ ║
║ Man└───────────────┘EN-BY: N Tiny SEEN-BY: N CPD: N Psive: N ║
║ Convert Umlaut: N Keep users: N Kill read: N Disble Psive: N ║
║ Remote changes: Y Hide area: N Keep NetMails: N ║
[...] [...]
║────────────────────────────────────────────────────────────────────║
║Press F10 to save or ESC to abort editing... ║
╚════════════════════════════════════════════════════════════════════╝
───────────────────────────────────────────────────────────────────────
- 73 -
FastEcho MANUAL - Tutorial - Data dropdown menu - Area Configuration -
───────────────────────────────────────────────────────────────────────
here you must select the right aka to use for this area, in accor-
dance with the uplink address where you import it from. FastEcho will
use this aka to insert the right net-address in your origin line and in
several other circumstances too. It may be extremely important to
insert the right area in this field, expecially if you use more that
one "Secondary NetMail Area" (one for each net you are involved in) to
allow FEUTIL program adequately import the NetMail messages in the
right NetMail area in relation to the "aka" they are addressed to. For
our tutorial place the selector on the 2:999/999.0 address and strike
the return key to continue.
5.5.3.1.10 - Mandatory
When you toggle this switch to "Y" status, then your downlinks
won't be able to 'unlink' this area by theirselves by sending an
"AreaFix" unlink-request because it will be rejected. If you toggle
this option to "Y", then only you will be able to unlink this area by
accessing FESetup area manager and changing it manually. When this flag
is enabled the "Passive" flag won't be honored either. (see the
"Passive" flag at paragraph 5.5.3.1.14). For our tutorial, leave this
flag disabled.
5.5.3.1.11 - Keep SEEN-BY
We have already talked about SEEN-BY and its meaning in chapter
5.5.2.9, so, now I believe you are sufficiently aware of them. The sta-
tus of this flag will determine if FastEcho will keep all the seen-by
lines of the tossed (imported) EchoMails storing them into your messa-
gebase or if it will strip them instead. The SEEN-BY lines, neverthe-
less, aren't very interesting because they don't contain meaningful in-
formation, furthermore they take up a lot of space in your messagebase;
They can be helpful only for debugging purposes when checking the mail-
routing functionality. If you switch this option in "Y" all the seen-by
lines will be kept, otherwise they will be stripped out. If, instead,
you want to keep the SEEN-BY lines in your messages but you also want
to make them hidden, then is possible toggle in this item the setting
"H" . For our tutorial, switch this item active toggling it to "Y".
5.5.3.1.12 - Tiny SEEN-BY
The present option will be useful for HOST, GateWay and HUBs system
only. By means of this function, in fact, FastEcho will strip, in your
SEEN-BY lines, all the systems that aren't present in the export-to
list for this area. This task is mandatory for GateWays but could be
useful for HUB systems too, in order to decrease the size of EchoMail
packets. However, keep in mind that stripping of SEEN-BY lines may
defeat some enhanced dupe checking methods, so only turn this switch on
if you know (and are allowed to) what you do.
5.5.3.1.13 - CPD Circular Path Detection
If you switch this toggle to its "Y" status, then you will activate
another FastEcho power to detect dupelicates in your incoming mail
packets. This detecting methods is based upon the presence, in each
EchoMail message, of a particular "kludge" called "PATH", this kludge
reports the path that the messages follow to reach your system, node by
node. (For a complete kludge list see the appendix B) If you activate
───────────────────────────────────────────────────────────────────────
- 74 -
FastEcho MANUAL - Tutorial - Data dropdown menu - Area Configuration -
───────────────────────────────────────────────────────────────────────
this feature, then FastEcho, when tossing your incoming mail packets,
will consider all the messages that already have your net address in
the ^APATH kludge, as dupes discarding them or copying them in the
DupeMail area.
5.5.3.1.14 - Passive
You will be able to set this flag only if the area you are configu-
ring has been set as "passthrough" (See 5.5.3.1.6) as storage method.
As said before, the "passthrough" is a particular setting that allows
you to forward EchoMail areas to your downlinks without storing them
locally on your system. (It can be useful when this area is unintere-
sting for you but not for your downlinks). This FastEcho's feature is
strictly related to the "Forward AreaFix Request" capability. We shall
see later that FastEcho, if you want, has the power to accept an
AreaFix "Link" request relating to areas that you aren't available on
your system, by forwarding it to your uplink that has it. FastEcho, in
this case, will automatically create one of its own AreaFix "Link"
requests, addressed to your uplink, setting the requested area as pass-
through and, directly, joining it to the downlink that requested it.
This "automatically" linked area will remain, from now on, available on
your system as "passthrough" area and other systems, if they want,
will be able to link up with it. If these systems decide to unlink this
area, they could send you an AreaFix "Unlink" request, thus, their
addresses will be removed, one by one, from the "Export-To" list until
it contains only the "Uplink" address; If it happens, this means that
this area will be tossed without storing or forwarding it. FastEcho
has the capability of detecting this behavior while processing the
AreaFix requests from your downlinks, thus it will try to unlink your
system from this, now, useless area, by sending an AreaFix "Unlink"
request spontaneously to your uplink and by automatically toggling the
"Passive" switch to "Y". If then, FastEcho receivesanother request for
such an area from your downlinks in order to reactivate this area,
FastEcho will switch this toggle to "N" activating this area again
and, simultaneously, it will send a new "Link" request to your uplink.
Keep in mind that, all this mechanism, works only if your uplink is
mentioned in the "Forward AreaFix Request" list (that we shall see
later). For our tutorial, leave this option disabled by toggling it to
"N".
5.5.3.1.15 - Convert Umlaut
This feature may be useful for German people only. As you certainly
know, there are some symbols and letters that you cannot use in FidoNet
EchoMail areas. In these forbidden letters are included the so called
German "Umlauts" (ÄäÖöÜüß). If you switch this option active, by swit-
ching it to "Y", then FastEcho will convert "on-the-fly" the "Umlauts"
into "EchoPol"-compliant characters while managing messages. As you
certainly remember, We have already met this option in "Node-Manager"
(See 5.5.1.14 chapter). Switch this option active, only if you write in
German using the "Umlaut" symbols. For our tutorial leave this option
disabled.
───────────────────────────────────────────────────────────────────────
- 75 -
FastEcho MANUAL - Tutorial - Data dropdown menu - Area Configuration -
───────────────────────────────────────────────────────────────────────
5.5.3.1.16 - Keep Users
This flag doesn't affect any FastEcho behavior. Infact, it works
over the FEUTIL companion utility when it performs the "purge" opera-
tion. If you enable this option, then, FEUTIL PURGE won't be able to
kill any still unread message which is addressed to any of the FastEcho
user you defined in the "User-names" list (See paragraph 5.4.2 for more
information) It could be useful if you, or any user previously defined
in "User-names", must leave the system for vacations or trips and you
don't want the normal system upkeep routines, performed with the FEUTIL
Purge/Pack commands to deletes your mail until you come back home. For
our tutorial leave this option disabled.
5.5.3.1.17 - Kill Read
This is another function for tuning the FEUTIL PURGE behavior. If
this switch is enabled, then the purge operation will involve all the
messages foregoing the last one you have read. This can be done thanks
to a particular file called "LASTREAD.BBS" that internally keeps track
of your last read message in every configured area. In this way all
the messages located before this kind of "bookmark" will be deleted.
This "Kill Read" function works separately from the normal "Purging Pa-
rameters" that hasn't any effect over these messages. For our tutorial
leave this option disabled.
5.5.3.1.18 - Disable Passive
This option is strictly related with the one seen in paragraph
5.5.3.1.14. As we have seen in the mentioned paragraph, FastEcho is
capable of automatically switching the "passthrough" areas to "Passive"
status when the last downlink sends to your system an AreaFix-Unlink
request. This toggle is provided to avoid this automatic switching; so,
enabling this option FastEcho won't generate any AreaFix unlink request
addressed to your Uplink even if none of your downlinks are currently
linked to this area. For our tutorial leave this option inactive by
switching it to "N".
5.5.3.1.19 - Remote changes
Its a very similar option to the "Mandatory" one, we have seen in
the chapter 5.5.3.1.10. If you enable this function, then FastEcho will
reject all the AreaFix requests that your downlinks may send to your
system, in order to link or unlink this area. The only difference be-
tween "Remote changes" and "Mandatory" is that, while "Remote changes"
is active, the "Passive" flag will be honored, with a "Mandatory" one,
it won't. (For an accurate explanation of the "passive" flag, see the
chapter 5.5.3.1.14)
───────────────────────────────────────────────────────────────────────
- 76 -
FastEcho MANUAL - Tutorial - Data dropdown menu - Area Configuration -
───────────────────────────────────────────────────────────────────────
5.5.3.1.20 - Hide Area
This option may be useful if you have, on your system, some private
areas that you wish to hide to some of your downlinks. By means of
AreaFix, your downlinks can request to your system a list of all your
available areas. If you don't wish to leave this area visible to all
your downlinks, simply enable this option, so it won't appear either in
the "%LIST" nor in the "%UNLINKED" metacommeds request. It will be vi-
sible only with the "%QUERY" and "%INFO" MetaCommands if the area is
linked to the specific system. For our tutorial keep this switch
disabled.
5.5.3.1.21 - Keep NetMails
This flag only operates upon the "NetMail" areas type and tells
FastEcho SCAN not to assign NetMail messages exported from this area
into your "Primary NetMail Area" the 'Kill/Sent' flag, which means
after sending these messages will remain in your NetMail area for later
processing (like back-up purposes).
5.5.3.1.22 - Purging
This section represent the selective purging conventions only for
the area you are defining. If one of the following items isn't speci-
fied (leaving it at zero value), then FEUTIL will take into due
consideration the global purging convention settled in chapter 5.4.9.1
(Purging defaults). Their meanings, that will be summarized below, will
be the same we have already seen in the chapter above mentioned but, if
you specify them here, they will be valid for this area only. In this
way you will be able to fine tune the purging parameters for every
single one of them.
5.5.3.1.22.1 - Purging (Msgs)
Here you may specify the number of messages you want to be kept in
this particular area after the "Purge" operation has been completed.
FastEcho will mark for deletion the messages that exceed this limit
starting from the older ones (see paragraph 5.4.9.1.1 for further
details about this option) For our tutorial, leave this option to "0".
5.5.3.1.22.2 - Purging (Days)
With the number specified here you will communicate to FEUTIL your
preferences about how old the messages in this area have to be before
it can start marking them for deletion while executing the Purge opera-
tion. For our tutorial leave this option to "0".
5.5.3.1.22.3 - Purging (Rcvd Days)
Here you may inform FEUTIL that you allow it to start marking for
deletion all messages carrying the 'Received' (read) flag older than
specified. For our tutorial leave this option to "0".
───────────────────────────────────────────────────────────────────────
- 77 -
FastEcho MANUAL - Tutorial - Data dropdown menu - Area Configuration -
───────────────────────────────────────────────────────────────────────
5.5.3.1.23 - Security
In the following two items you can define which security level the
area you are defining will have. The levels must be adjusted conformly
to the security level that the nodes, defined in your "Node Manager",
have, in order to allow them to link this particular area or not.
These security levels have only means for automated operations
performed from your downlinks through AreaFix "Link" requests and
whether or not messages in an area will be accepted from or send to a
specific system.
5.5.3.1.23.1 - Read (Security)
This is the security level that you wish to assign to this area.
If a downlink, having its own security level in node manager (see: Se-
curity - chapter 5.5.1.9) greater or, at least, equal to this "Read-
area-security", tries to link this area, its request will be honored;
if, instead, it has the security level lower than the one specified in
this item, then the request will be refused and the link denied. Remem-
ber that this switch gives to the downlinks, only the permission to
read this area. In this way you may leave some downlinks abled to Read
only this area even if they are currently linked. For this tutorial,
input in this field the number "10" and strike return to continue.
5.5.3.1.23.2 - Write (Security)
With this item you can bind the "Write-Security" at this particular
area. As said before, a downlink may have the permission to "read-on-
ly" a area if its node-security level is greater or equal only to the
one specified in "Read" security. If you want to leave the downlinks
also free to link this area in "Write", check that the "Node" se-
curity level is greater or, at least, equal to the "Area" security le-
vel you will input herein. For our tutorial, input the number "10" con-
firming with the "return" key.
5.5.3.1.23.3 - Examples (Security)
The node 2:888/888 has security level 100
The node 2:777/777 has security level 50
The node 2:666/666 has security level 30
The EchoMail area TEST0.CHT has security level 100 read and 100 write
The EchoMail area TEST1.CHT has security level 50 read and 50 write
The EchoMail area TEST2.CHT has security level 30 read and 40 write
The node 2:888/888 will be able to link all the EchoMail areas here
mentioned both in read/write because it has 100 as security level which
is higher than the area security level for TEST1 and TEST2 and equal to
the TEST3 read/write level. The node 2:777/777 will be able to link
only the TEST1 and TEST2 EchoMail area, because its security level is
greater than the read/write security level of the TEST2 area and equal
to the TEST1 read/write level. The node 2:666/666 will be able to link
in read-only the EchoMail area TEST2 because its security level is lo-
wer than the read/write security level of the TEST0 and TEST1 area and
furthermore, is lower that the "write" security level of the TEST2.
.-.-.
If you jumped in this section from the "Area Default Setting it's time
to go back to the chapter 5.5.2.9, otherwise follow on to the next one.
───────────────────────────────────────────────────────────────────────
- 78 -
FastEcho MANUAL - Tutorial - Data dropdown menu - Area Configuration -
───────────────────────────────────────────────────────────────────────
5.5.3.1.24 - SEEN-BY
We have already talked about "SEEN-BY" lines in the previous
5.5.2.9 chapter where its meaning and its application too has been ex-
plained, please refer to the mentioned paragraph for further informa-
tion about it. Here you will define the "SEEN-BY" item for this parti-
cular area you are defining. Placing the cursor upon the SEEN-BY item
and striking the return key. You will see the following box:
┌─────────────────┐
SEEN-BY:│■ >2:999/999< │
Export to:│ 16:999/999 │
└─────────────────┘
Whithin this Box are listed all your akas which match all your
addresses defined in the 5.4.1 chapter. You will be able to select one
or more between them simply by moving the highlighted box with the
arrows-key and tagging the SEEN-BY that fits your area requirements
with the Space-bar. When an Aka is tagged you can notice a small black
box to the left of the selected one. The SEEN-BY could be defined an
EchoMail tool; in fact it could be useful to trace EchoMail route
errors or to enable the FastEcho DupeChecking feature based upon the
SEEN-BY lines scanning. For our tutorial select the address 2:999/999
by tagging it and strike the "return" key to continue.
5.5.3.1.25 - Export-to
We extensively talked about the "Export-to" item in "Group Area De-
faults" in chapter 5.5.2.10. Here you may define manually which down-
link needs to be connected with the area you are now configuring but
remember that your downlinks could make the same operation by themsel-
ves by means of "AreaFix" Link requests (unless you decide differen-
tly). To access the "Export-to" dialog box, simply place the cursor
over the "Export-to" field; you will see the following screen:
╔═════════════════════════════ Edit Area ══┌─────────────────────────┐
║ Name: TESTECHO1 │ ■ 2:999/900.0 │
║ Comment: Exemplifying Board │ ■ 2:999/999.1 │
║ Origin: System in test@Fidonet.org │ 16:999/900.0 │
║ Type: EchoMail │ │
[...] [...] [...]
║ SEEN-BY: 2:999/999.0 │ │
║ Export to: 2:999/900.0 999.1 │ │
║──────────────────────────────────────────│ │
║Press F10 to save or ESC to abort editing.│ │
╚══════════════════════════════════════════└─────────────────────────┘
Any area, however, must contain in the "Export to" field, at least
one address: your uplink one. That's because you will pick up this area
from your uplink, but you must also send new EchoMail messages in this
area, locally created or received from your connected downlinks too. In
this field you had better insert immediately the address of your uplink
and, if you decide to configure them manually, the address of your
downlinks too; otherwise you can let them do the linking of their
preferred areas by themselves via "AreaFix" request. For our tutorial
you must select the address 2:999/900 and 2:999/999.1; the first one
is your uplink and the second one your downlink; then press return to
───────────────────────────────────────────────────────────────────────
- 79 -
FastEcho MANUAL - Tutorial - Data dropdown menu - Area Configuration -
───────────────────────────────────────────────────────────────────────
confirm your selection. You will notice that in the "Export-to" field,
the uplink address is reported complete while your downlink is reported
in abbreviated form. That's absolutely normal, it's done to save space.
.-.-.
Here you have finished the setup of the Area Configuration for your
first area. Now you need to repeat the steps from 5.5.3.1 until
5.5.3.1.25 as many times as many areas you want configured (by changing
the needed parameters, of course) When you finish all your areas then
press the "ESC" key to confirm the saving of all your inserted items
just when FESetup will ask you to do so. From now on I assume that you
have configured two EchoMail areas TESTECHO1 and TESTECHO2 for FidoNet,
two EchoMail areas TESTECHO3 and TESTECHO4 for ZyXELnet and one single
secondary NetMail areas called TESTNET, further I assume you already
have the "BadMail" mandatory area and the "DupeMail" areato enable the
dupechecking feature of FastEcho. So, when you return to the "area
browsing" your screen will look like the following:
FESetup System Data Export Import F1 Help
░░░░░░░░░░░░░░░░░░░░░░┌─────────────────────┐░░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░░░░░░░░░░│ Node-Configuration │░░░░░░░░░░░░░░░░░░░░░░░░
╔══ 1/7 ═══════════════════ Area-Manager ═══════════════════════════╗
║ Brd Area Name Used Aka Grp ║
║───────────────────────────────────────────────────────────────────║
║ 1 TESTECHO1 2:999/999.0 A ║
║ 2 TESTECHO2 2:999/999.0 B ║
║ 3 TESTECHO3 16:999/999.0 C ║
║ 4 TESTECHO4 16:999/999.0 C ║
║ 5 BADMAIL 2:999/999.0 D ║
║ 6 DUPEBOARD 2:999/999.0 D ║
║ 7 TESTNET 2:999/999.0 E ║
[...] [...]
╚═══════════════════════════════════════════════════════════════════╝
░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
Enter-Edit Ins-Add Del-Delete F2-Sort F3-Tag F4 Srch F5-Copy F6-Glbal
As you can see, at the bottom of this screen, are displayed some
active function keys that provide some facilities managing the already
defined areas: The "Enter" Key, F2 through F6 "Ins" and "Del" key.
Let's see each of them in detail.
5.5.3.1.26 - Active 'Area Manager' Function keys
5.5.3.1.26.1 - Area Manager (Enter-Edit)
While you are in "Area Browsing", by means of the "Enter" you will
be able to edit the parameters of the selected areas, thus, before
pressing it, make sure to select, with the arrows-key, the right area
you wish to edit. The editing layout will be exactly the same we have
seen when inserting the first area, so, I assume you already know it.
───────────────────────────────────────────────────────────────────────
- 80 -
FastEcho MANUAL - Tutorial - Data dropdown menu - Area Configuration -
───────────────────────────────────────────────────────────────────────
5.5.3.1.26.2 - Area Manager (F2-Sorting)
If you wish to see your area browsing sorted differently from the
default or if you wish to activate the speed search utility with your
preferred search-key, then you can use the "Sort" function. Simply by
pressing the "F2" key, the following box will pop up from the center of
the screen:
┌───────────────┐
│>Sort by Name< │
│ Sort by Group │
│ Sort by Board │
└───────────────┘
In this dialog box you can choose one of the available sort-keys by
moving the highlighted box with the arrows-key and confirm with "Re-
turn". You will see that the area browsing list is changed accordingly.
When the areas are sorted you will be able to use the speed search
function. Try, for example, to sort by "Name" and, from your area
browsing screen begin to finger the areatag "D"; you will see that im-
mediately the selector will be placed upon the first AreaName that
starts with "D" (in our case the "DupeMail" area). The other sorting
keys will work likewise, of course. If you sort by group, the speed-
search will work only over the area groups and if you sort by board it
will work over the assigned board number (and messagebase type for all
non-HMB areas).
5.5.3.1.26.3 Area Manager (F3-Tag)
The area tagging will be useful when you want to perform some ope-
ration involving only the selected ones. Normally you can "tag" an area
manually, simply by placing the highlighted box over it and pressing
the space-bar; when an area is tagged, you will see, as usual, the
small black box to the left of the tagged area. The FESetup Area-Mana-
ger provides an easier way to tag multiple area by using the tag faci-
lity. Try to press the "F3" key, immediately the following dialog-box
will be shown in the center of the screen where you can select your
preferred tagging methods.
┌──────────────┐
│>Tag by Name< │
│ Tag by Group │
└──────────────┘
5.5.3.1.26.3.1 - Tag by name
If you have a lot of areas in the Area-Browsing screen and you
exactly remember the areatag, then you can directly tag the area you
need simply by selecting "Tag by Name". You will see the following box:
╔═══════════════ Tag by Name ══════════════╗
║ _ ║
╚══════════════════════════════════════════╝
You can input herein the name mask of the areas you want to tag, for
which the usual '*' and '?' wildcards may be used. If FESetup is be
able to find your specified areas then theywill be immediately tagged,
otherwise no other action will take place.
───────────────────────────────────────────────────────────────────────
- 81 -
FastEcho MANUAL - Tutorial - Data dropdown menu - Area Configuration -
───────────────────────────────────────────────────────────────────────
5.5.3.1.26.3.2 - Tag by Group
This option can be useful if you want to tag entire groups of areas
with one single operation. The Area Manager (F3-Tag), in fact,allows
you to tag for group too. If the "Tag by Group" item is selected, then
you will be immediately prompted to select the group you want to tag by
means of the following dialog box:
FESetup System Data Export Import F1 Help
░░░░░░░░░░░░░░░░░░░░░┌──────────────┌───────────────────────────────┐
░░░░░░░░░░░░░░░░░░░░░│ Node-Configur│>A) Fidonet EchoMail area Intl<│
╔══ 1/7 ═══════════════════ Area-Man│ B) Fidonet EchoMail area Natl │
║ Brd Area Name │ C) ZyXELnet EchoMail area │
║───────────────────────────────────│ D) │
║ 1 TESTECHO1 │ E) │
║ 2 TESTECHO2 │ F) │
║ 3 TESTECHO3 │ G) │
║ 4 TESTECHO4 │ H) │
║ 5 BADMAIL │ I) │
║ 6 DUPEBOARD │ J) │
║ 7 TESTNET │ K) │
[...] [...] [...]
║ │ M) │
╚═══════════════════════════════════└───────────────────────────────┘
Enter-Edit F2-Sorting F3-Tag F4-Search F5-Copy F6-Globl Ins/Del-Entry
In this new box all your configured groups will be listed. You will
be allowed to select one of them and this will cause the automatic tag-
ging of all the areas belonging to the selected group. In the screen
shown above, for example, selecting the group "C", then the areas
TESTECHO3 and TESTECHO4 will immediately results tagged.
5.5.3.1.26.4 - Area Manager (F4-Search)
This function allows you to search an area by using of its name
without being compelled you to sort the whole defined area for the
specified key. It can be done simply by pressing the "F4" key, so you
will be prompted to input the area name you are looking for, by means
of the following box:
╔════════════════ Find Area ═══════════════╗
║ _ ║
╚══════════════════════════════════════════╝
By inputting the complete or abbreviated area name within this box
and pressing return, if FESetup will be able to find the area you
specified, the highlighted box will be immediately placed over the
searched area.
5.5.3.1.26.5 - Area Manager (F5-Copy)
This one represents a very helpful function that could save a lot
of your time when configuring FastEcho. By using this function, in
fact, you will be able to duplicate one area which is already defined
within Area-Manager. For Example, if you have to define 20 FidoNet
EchoMail areas that you pick up from the same uplink, you could define
the first one only and then you may duplicate it 19 times. Obviously,
───────────────────────────────────────────────────────────────────────
- 82 -
FastEcho MANUAL - Tutorial - Data dropdown menu - Area Configuration -
───────────────────────────────────────────────────────────────────────
every time you duplicate a area, you must, at least, change its name;
the fine tuning of the others duplicated areas could be done after you
have finished.
5.5.3.1.26.6 - Area Manager (F6-Global)
This is one of the most powerful FESetup features. with this, you
will be able to globally change every parameters of your areas by
selecting them from the groups they belong to. Within the area manager
browsing screen, pressing the "F6" Key, the following layout will be
shown on your screen:
╔═══════════════════════ Global changes ════════════════════════╗
║>Add Node< │ Mandatory ║
║ Delete Node │ Keep SEEN-BY ║
║ Replace Node │ Tiny SEEN-BY ║
║ with │ CPD ║
║ Origin │ Passive ║
║ Your Aka │ Disable Passive ║
║ SEEN-BY │ Convert Umlaut ║
║ Type │ Keep users ║
║ Purging # Days │ Kill read ║
║ # Rcvd Days │ Remote changes ║
║ # Msgs │ Hide area ║
║ Security Read │ Keep NetMails ║
║ Write │ Group ║
║──────────────────────────────────────────┴────────────────────║
║ Perform changes ║
╚═══════════════════════════════════════════════════════════════╝
With the only exception of the first three items (that will be se-
parately explained) the others are all "cut & paste" options. It means
that if you insert a value in one of them, then the corresponding value
present in your areas definitions will be stripped out and replaced
with the one that you defined in this layout. After having specified
the changes you wish to perform upon your defined areas, you will be
prompted to select the areas-group where you want your changes to take
place. Note: if you have currently tagged one or more areas, you can
perform the changes for all of them. When pressing F6 FESetup will ask
you if you want to do so and if answered yes, it will later on not ask
you for the groups to change but process all tagged areas. Let's now
see the first two options
5.5.3.1.26.6.1 - Global (Add Node)
This option will be very useful when you want to enable manually a
new downlink to receive certain EchoMail areas belonging to certain
specified areas/groups. Placing the higlighted box over the "Add Node"
item and striking the "return" key, you will be able to select the
address of the new downlink to be added by means of the following pop
up box.
───────────────────────────────────────────────────────────────────────
- 83 -
FastEcho MANUAL - Tutorial - Data dropdown menu - Area Configuration -
───────────────────────────────────────────────────────────────────────
╔═════════════════┌──────────────┐anges ════════════════════════╗
║ Add Node │>2:999/900.0< │ │ Mandatory ║
║ Delete Node │ 2:999/999.1 │ │ Keep SEEN-BY ║
║ Replace Node │ 16:999/900.0 │ │ Tiny SEEN-BY ║
║ with └──────────────┘ │ CPD ║
[...] [...] [...]
║──────────────────────────────────────────┴────────────────────║
║ Perform changes ║
╚═══════════════════════════════════════════════════════════════╝
As you can notice, the address listed in the box are the ones you
defined in "node manager" so, the new downlink you want to add by way
of the "Global Changes" feature, must already be inserted in the "node
manager" before you continue, otherwise you won't be able to select it,
of course. Here you can select, in the usual way, the address which you
want added in the areas belonging to the group we will specify later.
Pressing the "Return" key, the node you selected will be reported in
the "Add node" field. You can now place the selector-box upon the "Per-
form changes" and strike "return" again. FESetup, now, will ask you
what groups have to be involved for the specified changes (unless you
selected to perform the changes on all tagged areas before):
FESetup System Data Export Import F1 Help
░░░░░░░░░░░░░░░░░░░░░░┌──────────────┌───────────────────────────────┐
░░░░░░░░░░░░░░░░░░░░░░│ Node-Configur│■ A) Fidonet EchoMail area Intl│
╔══ 1/7 ════════════════════ Area-Man│■ B) Fidonet EchoMail area Natl│
║ Brd Area Name │ C) ZyXELnet EchoMail area │
║────────────────────────────────────│ D) │
║ 1 TESTECHO1 │ E) │
║ 2 TESTECHO2 │ F) │
║ 3 TESTECHO3 │ G) │
║ 4 TESTECHO4 ╔══════════ Groups ═│ H) │
║ 5 BADMAIL ║ AB │ I) │
║ 6 DUPEBOARD ╚═══════════════════│ J) │
║ 7 TESTNET │ K) │
[...] [...] [...]
║ │ W) │
╚════════════════════════════════════└───────────────────────────────┘
░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
Enter-Edit F2-Sorting F3-Tag F4-Search F5-Copy F6-Globl Ins/Del-Entry
The node you have previously specified in the "Add node" field will
be added,as active downlink, in all the areas belonging to the groups
you will tag in this new window. Tagging the groups can be done, as
usual, by placing the pointer-box upon the group you need and selecting
it with the "space-bar". A tagged group will be marked with a small
black box to the left. After the groups are selected, FESetup waits un-
til you press the "return" key to start the changing operations over
the specified areas. When FESetup finishes, a little info-box will no-
tify you about the number of areas that have been changed.
5.5.3.1.26.6.2 - Global (Delete Node)
This global option acts likewise the previous one but, instead of
adding a new node as active downlinks in the specified areas, this one
will work the opposite way by removing an existing downlink or uplink
from the groups you will specify.
───────────────────────────────────────────────────────────────────────
- 84 -
FastEcho MANUAL - Tutorial - Data dropdown menu - Area Configuration -
───────────────────────────────────────────────────────────────────────
5.5.3.1.26.6.3 - Global (Replace <Node> with <Node>)
This option allow you to specify a node (uplink or downlink) to be
stripped and contextually replaced with the one you will specify in the
"With" field. This feature can be considered as a mix between the pre-
vious two options. Here, FESetup will allow you to specify the node to
be stripped and the node to be replaced, by way of the usual selector
box. In this case the "Replace" operation will take place only if
FESetup is able to find the node to be stripped in the specified areas
belonging to the specified groups.
5.5.3.1.26.6.4 - Global (The other global items)
As mentioned before, all the other items work as "Cut & Paste" op-
tions. All items that can be cut and pasted, which are listed in the
"Global" layout, are referenced to the same items we met in the "Area
Configuration" section from chapters 5.5.3 until 5.5.3.1.24. In the
Global options you may strip and replace any of them in every group you
select.
5.5.3.1.26.7 - Area Manager (Ins/Del-Entry)
The use of these two keys is intuitive: you need them in order to
Ins(ert) new areas or Del(ete) the existing ones, according to your
needs. By pressing the "Ins" key you will be immediately prompted to
create a new area: FESetup will display on your screen an empty "Edit-
Area" layout, ready to be filled with new data. By pressing the "Del"
key you can mark one or more areas for deletion. The areas in fact,
won't be immediately removed but only marked for deletion. You will be
able to distinguish every "Marked" area by way of the "asterisk" (*),
visible to the left of the area tag. The area marked for deletion will
be then physically removed, after confirmation, exiting from the "Area
Manager" section. The "delete" operation could be done also by tagging
the areas you wish delete, by way of the "space-bar", and when you fi-
nish, by pressing the "Del" key or, furthermore, you can delete entire
groups in conjunction with the 5.5.3.1.26.3.2 option (tag by group). In
both cases, performing the mark-for-deletion operation via the "Del"
key, after you tagged one or more areas, FESetup will ask for your con-
firmation with the following box:
╔════════════════════════════╗
║ ║
║ Perform delete on tagged ║
║ areas ? (Y,N) ║
║ ║
╚════════════════════════════╝
Answering "Y" all the tagged areas will be marked for deletion,
otherwise, no action will take place.
.-.-.
Here you have finished the "Area Manager" section, now, pressing the
"ESC" key you will return to the "Data DropDown Menu"
───────────────────────────────────────────────────────────────────────
- 85 -
FastEcho MANUAL - Tutorial - Data dropdown menu - Carbon Copies -
───────────────────────────────────────────────────────────────────────
5.5.4 - Carbon Copies
-------------
FastEcho has the power to perform a very special operation while
tossing the incoming mail packets: It can detect, among the message
areas it processes (with the only exclusion of the BadMail Area), the
ones that have particular meaning for you and, then, it can copy one
duplicate of each of these messages into one or more personal areas.
This feature is called "Carbon Copy" function Naturally, if you plan to
use this feature, you should, beforehand, define the area (or the
areas) where your carbon-copied messages will be copied into, thus,
before starting to configure this option, define almost a new local
area for this purpose (you can call it, "PERSMAIL" for example) see at
the chapter 5.5.3.When you have done it exit, to the "Data Dropdown
Menu", move the highlighted box over the "Carbon Copies" item and
strike the "return" key. You will see the following layout:
FESetup System Data Export Import F1 Help
░░░░░░░░░░░░░░░░░░░░░░┌─────────────────────┐░░░░░░░░░░░░░░░░░░░░░░░░░
░╔══════════════════════════ Carbon Copies ═════════════════════════╗░
░║ Test for Store copy in area: ║░
░║──────────┬──────────────────────────────┬────────────────────────║░
░║ A) │ │ ║░
░║ B) │ │ ║░
░║ C) │ │ ║░
░║ D) │ │ ║░
[...] [...] [...] [...]
░║ G) │ │ ║░
░║ H) │ │ ║░
░║ I) │ │ ║░
░║ J) │ │ ║░
░╚══════════════════════════════════════════════════════════════════╝░
░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
Edit Carbon Copies (names, areas etc.)
In every EchoMail message that FastEcho can process, are present
some message-items that can be checked.They are the "From", "To", "Sub-
ject" and the "Kludge" items. In the Carbon Copies section, in fact,
FESetup can accept the contents specification for these items in order
to let FastEcho search them into your incoming mail packets while it
processes the mail. FESetup allows you to specify these parameters by
means of the shown layout. As you can see, it's subdivided into three
columns. In the first "Test" column you may specify in what item Fast-
Echo has to look; in the second "for" column you can point out what
FastEcho has to look for, relatively to the first specified item; fi-
nally, in the third item, you will specify in which area the messages
that match your previous specification have to be copied. Let's see
these three columns.
5.5.4.1 - Test
In the "Test" columnwe shall specify for which message-item Fast-
Echo has to look. Placing the cursor over the first slot of the "Test"
column and striking the "return" key a new dialog box will be shown to
you over the "Carbon Copies" main screen:
───────────────────────────────────────────────────────────────────────
- 86 -
FastEcho MANUAL - Tutorial - Data dropdown menu - Carbon Copies -
───────────────────────────────────────────────────────────────────────
FESetup System Data Export Import F1 Help
░░░░░░░░░░░░░░░░░░░░░░┌─────────────────────┐░░░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░░░░░░░░░░│ Node-Configuration │░░░░░░░░░░░░░░░░░░░░░░░░░
░╔══════════════════════════ Carbon Copies ═════════════════════════╗░
░║ Test for string Copy to ║░
░║───┌─────────┐───────────────────────────┬────────────────────────║░
░║ A)│>None< │ │ ║░
░║ B)│ From: │ │ ║░
░║ C)│ To: │ │ ║░
░║ D)│ Re: │ │ ║░
░║ E)│ ^A: │ │ ║░
░║ F)└─────────┘ │ ║░
[...] [...] [...] [...]
░╚══════════════════════════════════════════════════════════════════╝░
░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
As you have certainly know, every EchoMail message has a "From:"
item where, generally, the message sender is specified, a "To:" item,
where, normally, the message addressee is defined, and, last of all, a
"Re:" item where the message topic is described. The aforesaid are
"normal" message items but, an EchoMail message, may also have an unde-
termined number of special "item" called Kludges that FastEcho can
test. These kludges, although they are always present, are normally
hidden to the receivers (unless its message editor is capable of fin-
ding them) and they have always the "^A" pair of characthe at their
beginning. For a complete Kludge list, see in appendix B. In this
dialog box, so, you may select what item you wish FastEcho to tests.
Place the higlighted box over the item you need and strike return. The
item you have choosen will now be shown in the first slot of the "Test"
column, while, the cursor will be placed over the corresponding slot
in the "for" column. For our tutorial select in this box the "To:" item
and strike the "return" key to confirm.
5.5.4.2 - For string
After you have defined in what item you want FastEcho to search
for, you will be immediately prompted to input the string that FastEcho
has to search for, within the specified item (on the same row). If you,
in the "Test" column, selected the "To:" item, then, in all probabili-
ties, you will specify in this item your first and second name, or your
alias or, moreover, the string "SysOp"; By doing so, you will bind
FastEcho to detect in all the incoming mail, all the messages addressed
"To:" you and copy them in a particular area that you will specify in
the next paragraph. For our tutorial, input in this field the string
"Reed Richard" and strike the return key.
5.5.4.3 - Copy to
After having defined where and what to search for, you will be
prompted to select your particular area where you want the messages
matching your specifications to be duplicated. By placing the cursor
over "Store copy in area:" the following dialog box will be shown to
you:
───────────────────────────────────────────────────────────────────────
- 87 -
FastEcho MANUAL - Tutorial - Data dropdown menu - Carbon Copies -
───────────────────────────────────────────────────────────────────────
FESetup System Data Export Import ┌───────────────┐
░░░░░░░░░░░░░░░░░░░░░░┌─────────────────────┐░░░░░░░░│ 1 TESTECHO1 │
░░░░░░░░░░░░░░░░░░░░░░│ Node-Configuration │░░░░░░░░│ 2 TESTECHO2 │
░╔══════════════════════════ Carbon Copies ══════════│ 3 TESTECHO3 │
░║ Test For string Copy to │ 4 TESTECHO4 │
░║──────────┬──────────────────────────────┬─────────│ 5 BADMAIL │
░║ A) To: │ Reed Richard │ │ 6 DUPEBOARD │
░║ B) │ │ │ >8 PERSMAIL< │
░║ C) │ │ │ 7 TESTNET │
░║ D) │ │ │ │
[...] [...] [...] [...] [...]
░╚═══════════════════════════════════════════════════│ │
└───────────────┘
In this new dialog-box you will be able to select the aforesaid
area where the found messages will be duplicated. Make sure not to se-
lect any EchoMail areas for this purpose unless you have particular
reason to do so. Normally the "Carbon-Copied" messages have to be co-
pied in a local-area customly created.
5.5.4.4 - Examples
You need to detect all messages sent by "Sue Wright" and to store their
copies to your persmail area:
Test : From:
For string : Sue Wright
Copy to : PERSMAIL
You need to detect all messages addressed to your CoSysOp and to store
their copies in persmail area:
Test : To:
For string : Jonny Storm
Copy to : PERSMAIL
You need to intercept and store in your personal area all messages
having "FastEcho" as topic.
Test : Subj:
For string : FastEcho
Copy to : PERSMAIL
5.5.4.5 - Suggestions and notes
Using the "Carbon Copies" feature you must be aware that the com-
parision of the strings contained in the fields you specify, will be
"case insensitive" ; furthermore, FastEcho won't check inside the
fields you specify in "Test" slot for an exact match but it will start
to search inside it from the beginning to end, checking if it's at
least contained in it. It means that if you test the "To:" field for
"Martin" all mails containing any 'martin' as addressee, will be co-
pied - mails to 'Martin Miller' as well as mails to 'John Martinelli'.
So don't let FastEcho test for short strings as it would cause it to
copy many mails more, than you wanted to. This does not apply to the
'Kludges' search, where the pattern will only be compared beginning
with the first character after the ^A character.
───────────────────────────────────────────────────────────────────────
- 88 -
FastEcho MANUAL - Tutorial - Data dropdown menu - What's AreaFix -
───────────────────────────────────────────────────────────────────────
5.5.5 - What's AreaFix
--------------
In this manual we have seen the "AreaFix" mentioned several times
But what really is "AreaFix"? AreaFix is an automated procedure, inte-
grated in FastEcho, that allows several operations upon your system
configuration to be performed from your downlinks directly, without any
your manual intervention. They simply have to send a NetMail message to
your system, addressed directly to AreaFix. Your FastEcho, when it de-
tects such message in the primary NetMail area, will process it per-
forming, automatically, all the changes and, furtermore, it will gene-
rate an AreaFix report, addressed to the requesting downlink, that
reports all the results. An example of AreaFix header message is repor-
ted below:
----------------------------------------------------------------------
Msg : 1 of 1 Uns Pvt Loc K/s
From : Franklin Richard 2:999/999.1 Wed 31 Dec 94 00:00
To : AreaFix 2:999/999.0
Subj : PASSWORD <- AreaFix password
----------------------------------------------------------------------
[...]
MetaCommands
[...]
----------------------------------------------------------------------
This example shows an AreaFix request header that your downlink may
send you. Remember that the "To:" field must contain the word "AreaFix"
while the destination address must be the exact address of the system
where the changes have to be performed. In the "Subj:" field the Area-
Fix "Password" agreed between you and your downlink must exist and, in
the message text the AreaFix MetaCommand must be present (we shall
point these out, one by one, in the next paragraph.) In your configu-
ration, you must set the AreaFix password in accordance with every node
settled in "Node Configuration" (see: 5.5.1.5.2 paragraph).
5.5.5.1 - AreaFix MetaCommands
As said before, the message-text of an AreaFix request must contain
one or more AreaFix MetaCommands. They are commands that FastEcho can
interpret while executing it from the dos-prompt by imputting:
FastEcho Afix
Each one of these commands has its specific function. Let's see them.
5.5.5.1.1 - Linking one or more new areas
If you want to join a new conference, it's enough to specify the
conference's tag in the text of your AreaFix request. In the AreaFix
body text it is possible to specify as many conference's tags as you
need, there are no limits. For example, if you are the system
2:999/999.1 and want to link the areas TSTECHO5_WRD, TSTECHO6_WRD and
TSTECHO7_WRD from your uplink (2:999/999), your AreaFix request will
look like this:
───────────────────────────────────────────────────────────────────────
- 89 -
FastEcho MANUAL - Tutorial - Data dropdown menu - What's AreaFix -
───────────────────────────────────────────────────────────────────────
----------------------------------------------------------------------
Msg : 1 of 1 Uns Pvt Loc K/s
From : Franklin Richard 2:999/999.1 Wed 31 Dec 94 00:00
To : AreaFix 2:999/999.0
Subj : PASSWORD <- AreaFix password
----------------------------------------------------------------------
TSTECHO5_WRD
TSTECHO6_WRD
TSTECHO7_WRD
----------------------------------------------------------------------
Obviously, instead of "PASSWORD", the real password agreed between
you and your uplink must be present.
You may also add a '+' sign before each name (e.g. "+TSTECHO5_WRD").
5.5.5.1.2 - Unlinking one or more uninteresting areas
The procedure of unlinking an area that has become useless for you
is like the one you have already seen in order to link it. The only
difference is that, when you want to unlink one or more areas, you must
specify them preceded by the minus sign (-). For example, if you want
to unlink the EchoMail areas TSTECHO7_WRD and HOLYWARS_WRD from your
downlinks, then the message's body of your AreaFix request will look
like the following:
-TSTECHO7_WRD
-HOLYWARS_WRD
5.5.5.1.3 - Wilcarded Link/Unlink
FastEcho allows you the use of the WildCard characters, in your
AreaFix requests, while defining the areas to be linked or unlinked.
The use of the wildcard within the AreaFix request is absolutely "Dos-
alike". This wilcarded link/unlink may be useful when you have a lot of
areas to link or unlink that have some commomn characters in their tag
names. Here below I shall report an example: If you want to join from
your uplink all the areas that begin with KIDS, than you must input in
your AreaFix body text the following command:
KIDS*
If you want, instead, to unlink the same areas, it will be enough to
precede the command we seen, with the minus sign:
-KIDS*
This will link/unlink areas such as KIDSLINK, KIDSMOVE, KIDSCHAT and so
on. If you want to link all your available areas, then, simply send an
AreaFix message with an asterisk in its body, on the countrary, if you
want to physically unlink them, then send the asterisk preceeded by the
minus sign. As wildcard characters you have available the question mark
too. The question mark represents the positional macro substitution.
Here is another example: If you want to link the areas TBL01GER,
TBL03GER and TBL34GER but not the TBLITEM, TBLWORLD, TBL55HOL, with a
single operation you can do it by using the (?).It will be enough to
input in your AreaFix body text the following command:
───────────────────────────────────────────────────────────────────────
- 90 -
FastEcho MANUAL - Tutorial - Data dropdown menu - What's AreaFix -
───────────────────────────────────────────────────────────────────────
TBL??GER
It's obvius that, the unlinking operation will be done by preceding
this specification with the minus sign in this case too. The (*) and
(?) wildcards may be used both separately or in combination according
to your needs. The asterisk wildcard may also be used to link or
unlink all your available areas:
by typing the asterisk sign in your areafix message body to link all
the areas left available to you by your uplink:
*
or the asterisk preceded by the minus sign to unlink them:
-*
5.5.5.1.5 - %QUERY
When FastEcho processes an AreaFix message having the %QUERY
metacommand in its body, it will answer with an automatic generation of
a NetMail report containing a list of all the active areas that the
sender of this AreaFix request currently has. The NetMail will be, of
course, automatically forwarded to the node that requested it. Note
that if the areafix request message has the PGM ^aFLAG set, then
FastEcho won't include the requested list.
5.5.5.1.6 - %INFO
This MetaCommand will force the FastEcho AreaFix processor to gene-
rate a NetMail message containing a lot of useful information about the
agreements between you and your downlinks such as: his NetMail and ARC-
mail addresses, your aka, the AreaFix and the ARCmail password, the
agreed archiver and the ones that you have available on your system, a
brief statistic about received and sent EchoMails and, at last of all,
a list containing all active areas for his node. Sending an AreaFix
"NOTIFY" message may be helpful to your downlink at the first link in
order to summarize your agreements.
5.5.5.1.7 - %LIST
This MetaCommand has the purpose to point out all the EchoMail
areas that you have available on your system for the downlink that sent
you the AreaFix message containing "%LIST". In the report that FastEcho
will automatically create, won't be displayed, of course, the areas
that the requesting downlink can't access because of its security level
or its available groups. The areas with the "Hide Area" toggle turned
on won't be displayed either. see: 5.5.3.1.20)
5.5.5.1.8 - %UNLINKED
Processing this MetaCommand FastEcho AreaFix will generate a list
of the areas currently unlinked that the requesting system has. In this
case also will be listed only the EchoMail areas that the requesting
downlink can access to.
───────────────────────────────────────────────────────────────────────
- 91 -
FastEcho MANUAL - Tutorial - Data dropdown menu - What's AreaFix -
───────────────────────────────────────────────────────────────────────
5.5.5.1.9 - %AVAIL
This MetaCommand is strictly connected with the "Forward AreaFix
Request" feature that we will see later in this manual. As you will
see, a downlink can request an EchoMail area that you haven't available
but your uplink has. FastEcho, if correctly configured and only if you
want, will be able to redirect your downlink's AreaFix request to your
uplink in order to join the areas that the downlink wants. In
particular, when one of your downlinks sends you an AreaFix request
containing the "%AVAIL" MetaCommand in it, then FastEcho will answer it
with the list of all EchoMail areas that YOUR UPLINK has. Naturally,
you might have, in a file on your system, the complete list of the
areas imported from (or available on) your uplink but that you have
(not necessarily) connected. We see, later, where and how specify this
"list" file and what format it must have. If the uplink hasn't any
aforesaid forward area-list on its system, when %AVAIL is requested by
a downlink then AreaFix automatically answers with a proper error
message.
5.5.5.1.10 - %PAUSE
This AreaFix MetaCommand may be useful when a downlink needs to
stop calling your system to pick up its mail for a long period. By sen-
ding to your system an AreaFix message containing the "%PAUSE" it will
be automatically switched to passive status and, so, no more EchoMail
will be forwarded to a requesting system until it sends back, to your
system, another AreaFix request containing the "%RESUME" metacommand.
Note that when AreaFix switches a downlink to passive status a down-
link, its area won't be physically unlinked but only suspended.
5.5.5.1.11 - %RESUME
As said in the previous paragraph, the "%RESUME" MetaCommand will
be necessary to your downlinks in order to resume the forwarding opera-
tion of their mail previously suspended by way of the "%PAUSE" MetaCom-
mand. As soon as the "%RESUME" MetaCommand is processed by "FastEcho
AreaFix", all the areas that were active before the forward of the
first "%PAUSE" MetaCommand will be reactivated exactly as they were
before.
5.5.5.1.12 - %NOTE
Under normal circumstances AreaFix request messages will be deleted
after executing the requested commands. If you want to leave the sysop
of that system a comment (together with the original request message)
you can do so by adding a %NOTE command as the last command and AreaFix
will stop processing (ignoring the text you may write after the %NOTE
line) and will not delete the original request after being successfully
processed.
5.5.5.1.13 - %RESCAN
This is a very powerful AreaFix MetaCommand. When you link a new
area from your uplink, then you will start to receive the mail belon-
ging to it only the day after you linked it. It could happen that you,
instead, need to receive older messages that are already present at the
uplink system. In this case AreaFix can help you by means of its %RE-
───────────────────────────────────────────────────────────────────────
- 92 -
FastEcho MANUAL - Tutorial - Data dropdown menu - What's AreaFix -
───────────────────────────────────────────────────────────────────────
SCAN MetaCommand. When in the body of your AreaFix request you will in-
put the %RESCAN MetaCommand followed by one or more areas, the FastEcho
AreaFix makes two main operations:
1 - It checks if the areas you specified after the %RESCAN MetaCommand
are already linked or not. If they aren't linked then AreaFix will
immediately link them your system.
2 - It looks into the requested area in the Uplink's messagebase in or-
der to gather the messages contained in it in a mail packet, archi-
ving it and placing the generated mail bundle in outbound, ready to
be sent to your system at your next call.
As you can understand, relying upon this feature, may be a great
comfort. For example: If you want to join, from your uplink, the areas
MSD_SOFT.ITA and MSD_HARD.ITA and, contextually, also want to pick up
all the messages present upon the Uplink messagebase relatively to these
two areas, then you will input, in the message-text of your AreaFix
request, the Following lines:
%RESCAN
MSD_SOFT.ITA
MSD_HARD.ITA
You, furthermore will be able to fine tune the number or the age of
messages, that you want to be included in the rescanned mail packets by
means of the next two MetaCommand.
5.5.5.1.14 - %DAYS <nnn>
This MetaCommand works in conjunction with the %RESCAN. It is needed
in case you want the rescan operation to involve only the messages
received the last <nn> days (not older than <nn> days) within the area
that follow the %DAYS MetaCommand. If, for example you need to link the
area FLIPPER.ITA and contextually rescan it in order that the already
present messages, not older that a week can be sent to you, your AreaFix
message will look like the following one:
%RESCAN
%DAYS 7
FLIPPER.ITA
5.5.5.1.15 - %MSGS <nnn>
Like the %DAYS MetaCommand, this one, works only if coupled with the
%RESCAN. This is needed in case you want the rescan operation to involve
only the last <nn> messages, in the areas specified after the %MSGS
MetaCommand. If, for example, you want to link and, contextually, rescan
the area PINBALL.GER, in order that the last 100 already present messa-
ges will be sent to you, your AreaFix message will look like the follo-
wing:
%RESCAN
%MSGS 100
PINBALL.GER
───────────────────────────────────────────────────────────────────────
- 93 -
FastEcho MANUAL - Tutorial - Data dropdown menu - What's AreaFix -
───────────────────────────────────────────────────────────────────────
You can also use the two enhancement %RESCAN commands together. If,
for example, you wish to rescan (or link and rescan) the EchoMail areas
SPAGHETTI.ITA and CUCINA.ITA in order that the last 200 messages, not
older than 10 days can be sent to your system, then your AreaFix meta-
command will look like the following:
%RESCAN
%MSGS 200
%DAYS 10
%SPAGHETTI.ITA
%CUCINA.ITA
5.5.5.1.16 - %COMPRESS <Type> <?>
We have seen, in the 5.5.1.7 paragraph, that any downlink can have
an archiver (compressor) defined in FESetup, in order to let FastEcho
produce the mail bundles in order to be successfully unarchived (uncom-
pressed) from your downlink that uses the same compressor type. Normally
the definition of the compressor type must be agreed between the uplink
and the downlink. By means of this AreaFix MetaCommand, now, this
definition can be fully automated. your downlinks (and you with your up-
links) can now simply send to your system an AreaFix message containing
the %COMPRESS MetaCommand followed, on the same line, by the Tag of the
compressor type. If you, for example, want to change your compressor
type in ARJ, then you must send an AreaFix message, addressed to your
uplink, that has the MetaCommand in the body text:
%COMPRESS ARJ
if, on the other hand, before switching the compressor type, you
wish to know what compressor types are available on your uplink system,
then send to your uplink the same MetaCommand but with the trailing
question mark:
%COMPRESS ?
your Uplink's AreaFix will answer you with a NetMail message where
it will list all the available compressor with their tags needed to
activate each of them.
5.5.5.1.17 - %PWD <password>
As we have seen in paragraph 5.5.1.5.2, in order to allow a downlink
to perform AreaFix request you must, first, agree to one common password
with it. If FastEcho detects that the password matches, the AreaFix re-
quest will be correctly performed, otherwise no action will take place.
Well, once you have agreed the first password with your downlink, then,
by means of this metacommand, they will be able to change it when they
want. By sending an AreaFix request which contains in its text the meta-
command %PWD followed, on the same line, by the new password they want
to use, will be enough. For example, if you want to change your AreaFix
password in MYPASSW you must specify the MetaCommand as follows:
%PWD MYCOMMAND
───────────────────────────────────────────────────────────────────────
- 94 -
FastEcho MANUAL - Tutorial - Data dropdown menu - What's AreaFix -
───────────────────────────────────────────────────────────────────────
5.5.5.1.18 - %PKTPWD <password>
We have seen in paragraph 5.5.1.5.1 that, an ARCmail packet may have
its password, in order to enable the full security system provided by
FastEcho (see: 5.4.7.14). With this MetaCommand your downlinks (or you
with your uplink) can also change their ARCmail password. The command
Syntax will be the same as we have seen for the %PWD command: The meta-
command %PKTPWD directly follwed, on the same line, by the new password
you want to be used, from now on, for the ARCmail bundle security. If
you, for example, need to change your ARCmail password in "NEWARC" then
you must specify the AreaFix command as follows:
%PKTPWD NEWARC
5.5.5.1.19 - %FROM <net address>
It's a really powerful AreaFix MetaCommand. When inserted at the be-
ginning of your AreaFix request, all the MetaCommand that follows this
one will be performed as they were made from the node specified in %FROM
<net address>. This implies that any node, if qualified to do so, can
upkeep your system, so, this function could be useful if you want leave
to one full-confidence and reliable SysOp the task of keeping the ordi-
nary maintenance of your system meanwhile you are absent. For example,
you are the node 2:999/999 and your downlink 2:999/991 (Tony Stark),
being qualified to perform the remote maintenance, has to link and re-
scan the last 100 messages not older than 15 days the areas
COMMS_MODEM.ITA and COMMS_PHONE.ITA, to another downlink of your system:
the point 2:999/999.1; furthermore, it has to change the compressor for
this point to ZIP, create a report with the linked areas and, finally,
leave a message to inform you about the changes. The AreaFix message
will look like the following one.
----------------------------------------------------------------------
Msg : 2 of 2 Uns Pvt Loc K/s
From : Tony Stark 2:999/991 Wed 31 Dec94 00:05
To : AreaFix 2:999/999.0
Subj : PASSWORD <- AreaFix password
----------------------------------------------------------------------
%FROM 2:999/999.1
%RESCAN
%MSGS 100
%DAYS 15
COMMS_MODEM.ITA
COMMS_PHONE.ITA
%COMPRESS ZIP
%QUERY
----------------------------------------------------------------------
5.5.5.1.20 - %HELP
By means of this last command it will be possible for your AreaFix
to generate an help message containing a summary of all your AreaFix me-
tacommands with a brief explanation about their use. The help message is
fully configurable by you (as we shall see later) while the default help
file is named "AreaFix.hlp". To obtain the automatic AreaFix forwarding
of this "help file" it will be enough to specify the MetaCommand %HELP,
in the text of the request.
───────────────────────────────────────────────────────────────────────
- 95 -
FastEcho MANUAL - Tutorial - Data dropdown menu - What's AreaFix -
───────────────────────────────────────────────────────────────────────
5.5.5.1.21 - %EXPORT
This MetaCommand may be useful whenever you have previously suspen-
ded the mail-forwarding on your uplink with the MetaCommand %PAUSE (seen
before in the chapter 5.5.5.1.10). Even if your system is actually pau-
sed, by using the facility provided with the %EXPORT MetaCommand all
echomail messages having your name as addressee will be exported to you
all the same. In fact, when your uplink processes an areafix request
sent by you containing the MetaCommand %EXPORT, then it switches your
system in "export-by-name" status.
5.5.5.1.22 - %NOEXPORT
The %NOEXPORT is needed only if you want disable the feature you
activated before by using the %EXPORT MetaCommand.
5.5.5.1.23 - %QUIT
When the FastEcho encounters this metacommand it stop parsing the
current request. The same behaviour happens when an "-- " sequence is
found as internet signature start.
5.5.5.1.24 - Special %RESCAN syntax
FastEcho has the ability to offer you an alternative and quick way
to perform the %RESCAN operation by using an abbreviated form. This can
be done by specifying, in the areafix-request-message body, the name
(tag) of the area you want to rescan (or link and rescan) followed by a
comma, one space and the letter "R".
I.e. to rescan (or link and rescan) the area FASTECHO.ITA you can
use the following syntax:
FASTECHO.ITA, R
You can further fine tune your rescan operation specifyng the maxi-
mum number of messages you wish to be rescanned in the wanted area. This
can be done adding the equal sign and the limit number immediately after
the letter "R" as shown in the following example:
FASTECHO.ITA, R=100
It's further possible rescan all your linked areas by using another
special command after the %RESCAN MetaCommand:
%RESCAN
=*
it will cause the complete rescanning of your currently linked areas
without the need of specifying them one by one.
5.5.5.1.25 - Special AreaFix MetaCommands
Is possible to remove and/or rename any area from/of your configu-
ration via AreaFix directly. Doing these operation by mean of AreaFix
can give you great convenience because FastEcho will automatically
forward the changes you made in your configuration to your downlinks's
AreaFix or, alternatively, as an human readable information message.
───────────────────────────────────────────────────────────────────────
- 96 -
FastEcho MANUAL - Tutorial - Data dropdown menu - AreaFix Options -
───────────────────────────────────────────────────────────────────────
Deleting areas from your configuration: ~<AREA TO DELETE>
You can delete any areas from your FastEcho configuration by
specifying the area name preceded by the ~ (tilde) prefix. I.E. If you
want remove from your configuration the area ECHO_333.WRD you must write
~ECHO_333.WRD
in your AreaFix message's body.
Renaming areas from your configuration: &<OLD_AREA_NAME> <NEW_AREA_NAME>
If instead you want rename the area ECHO_333.WRD as ECHO_333.ITA you
can do it by using the prefix & (ampersand) followed by the original
name of the area to rename, one space, and the new name of the area:
&ECHO_333.WRD ECHO_333.ITA
The changes will be forwarded to your downlinks automatically in
this case too.
5.5.6 - AreaFix Options
---------------
After we explained, in chapter 5.5.5, what AreaFix does, now it's
time to start with the "AreaFix Option" section. In this chapter we
shall fine tune all the AreaFix default values and its advanced options
in order to obtain, from your system, a better performance; Furthermore,
within this chapter, we shall see and configure the "Forward-Areafix-Re-
quest" function. Now, from the "Data DropDown Menu" place the high-
lighted box over the "AreaFix Option" item (which is the last one) and
strike the return key. Immediately you will see this new menu:
FESetup System >Data< Export Import F1 Help
░░░░░░░░░░░░░░░░░░░┌─────────────────────┐░░░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░░░░░░░│>Node-Configuration< │░░░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░░░░░░░│┌────── AreaFix Options ─────┐░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░░░░░░░││ Allow %RESCAN Yes │░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░░░░░░░└│ └─Rescan defaults │░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░░░░░░░░│ Allow %PWD Yes │░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░░░░░░░░│ Allow %PKTPWD Yes │░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░░░░░░░░│ Allow %COMPRESS Yes │░░░░░░░░░░░░░░░░░░░░
░░░Copyright 1991-94│ Keep requests Yes │ rights reserved.░░░
░░░░░░░░░░░░░░░░░░░░│ Keep receipts Yes │░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░░░░░░░░│ Scan before tossing No │░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░░░░░░░░│ Detailed %LIST Yes │░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░░░░░░░░│ Add list to Receipt Yes │░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░░░░░░░░│ Passwords in %INFO No │░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░░░░░░░░│ Send conference rules No │░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░░░░░░░░│ └─Rulefile area tag prefix │░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░░░░░░░░│ Max. Receipt size 0 │░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░░░░░░░░│ AreaFix %HELP file │░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░░░░░░░░│ Forward Requests │░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░░░░░░░░└────────────────────────────┘░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
Allow %RESCAN MetaCommand in AreaFix requests
───────────────────────────────────────────────────────────────────────
- 97 -
FastEcho MANUAL - Tutorial - Data dropdown menu - AreaFix Options -
───────────────────────────────────────────────────────────────────────
5.5.6.1 - Allow %RESCAN
As we have seen in chapter 5.5.5.1.13, AreaFix has the capability of
rescanning the specified areas, upon your uplink's messagebase, in order
to gather the already present messages, pack and send them to the down-
link that sent to your system the AreaFix request. With this toggle you
can enable or disable this AreaFix function. If it is possible you will
also have access to the "Rescan Defaults" item. For our tutorial toggle
this item to "Y"
5.5.6.2 - Rescan Defaults
We have seen in chapters 5.5.5.1.14 and 5.5.5.1.15 that the %RESCAN
metacommand may be tuned directly within the same AreaFix request used
to order the %RESCAN operation, by means of the %MSGS and %DAYS metacom-
mand but, when a rescan operation is performed without any parameters,
then the whole area contents will be rescanned and sent to the reques-
ting downlink. You can, instead, limit the default rescan feedback by
setting the "defaults for rescan" in days or messages. Moreover you can
also limit the number of messages that a downlink can request, although
it uses the %MSGS or %DAYS MetaCommands. Place the cursor over the re-
scan default item and strike "return" and you will see the following
window:
┌────── Rescan defaults ─────┐
│>Default for rescan:< ALL │
│ ├─Default for %DAYS 0 │
│ └─Default for %MSGS 0 │
│ Maximum for %DAYS 0 │
│ Maximum for %MSGS 0 │
└────────────────────────────┘
5.5.6.2.1 - Default for rescan
This setting will define the behavior of the AreaFix processor when
it executes an AreaFix %RESCAN MetaCommand (See:5.5.5.1.13 and 5.5.61
paragraphs). This switch has three possible values: ALL, MSGS and DAYS.
Toggling it to "ALL", then, your settings in MSGS and DAYS won't be ta-
ken in consideration because, by default, all the messages contained in
the specified area (or areas) will be completely involved. For our tuto-
rial leave in this field the "ALL" toggle. By setting it in MSGS or
DAYS, instead, you will be able to access the items below for the fur-
ther definitions:
5.5.6.2.1.1 - Defaults for %MSGS
By setting the previous switch to "MSGS" you will be able to access
the Defaults for %MSGS item. The number you will specify here represents
the number of messages that will be taken in consideration for the Area-
Fix %RESCAN MetaCommand when no further limitation in "number of messa-
ges to rescan" has been specified.
───────────────────────────────────────────────────────────────────────
- 98 -
FastEcho MANUAL - Tutorial - Data dropdown menu - AreaFix Options -
───────────────────────────────────────────────────────────────────────
5.5.6.2.1.2 - Defaults for %DAYS
The "DAYS" toggle works like the previous. In fact, by setting the
"Default for rescan" in "DAYS" you will be able to access the present
item: "Default for %DAYS"; in this item you may specify the default
value for messages' old-age, pratically, the admittible rescanned messa-
ges will never be older than the number of days specified by means of
this item.
5.5.6.2.2 - Maximum for %DAYS
The "Maximum for %DAYS" item could be useful if you want to define a
limit for the eventual %DAYS MetaCommand that, in AreaFix requests,
could follow the %RESCAN. If you, in this item insert, for example, the
number 12, then, although the request for %DAYS, in the AreaFix request
may be higher than 12, it will be limited, in any case, to this value.
For the tutorial leave this field blank.
5.5.6.2.3 - Maximum for %MSGS
The "Maximum for %MSGS" works like the previous one, but, instead of
limiting the messages' age it will limit the maximum number of messages
involved by the %MSGS MetaCommand as regards to what's specified in the
AreaFix messages. If you insert in this item the number 100, then, also
if the request for %MSGS will report 500, the maximum number of messages
that will be rescanned will always be 100. For our tutorial leave this
field blank
5.5.6.3 - Allow %PWD
This toggle defines if you allow, or not, that your downlinks chan-
ge their AreaFix password by using the %PWD MetaCommand in AreaFix re-
quests. If you switch this toggle to "N" then FastEcho will ignore any
%PWD MetaCommand (For further information about the %PWD see also para-
graph 5.5.5.1.17). For our tutorial toggle this option in "Y" status.
5.5.6.4 - Allow %PKTPWD
Like the previous one, this toggle, defines if you allow, or not,
that your downlinks change their Packet password by using the %PKTPWD
MetaCommand in their AreaFix request (For further information about the
%PKTPWD see also the paragraph 5.5.5.1.18) For our tutorial leave this
option in "Y".
5.5.6.5 - Allow %COMPRESS
This switch will bind FastEcho to accept the %COMPRESS MetaCommand,
in order to change their Mail Packets compressor, processing it or not
in accordance with the status of this toggle. If it is set to "Y", then
the processing of %COMPRESS MetaCommand will be honored, otherwise it
will be completely ignored. For further information about the %COMPRESS
MetaCommand see also the paragraph 5.5.5.1.16). For our tutorial toggle
this option to "Y"
───────────────────────────────────────────────────────────────────────
- 99 -
FastEcho MANUAL - Tutorial - Data dropdown menu - AreaFix Options -
───────────────────────────────────────────────────────────────────────
5.5.6.6 - Keep requests
By default the AreaFix system kills any request after being proces-
sed. If you toggle this option to "Y", they won't be killed and will be
markedonly as 'Received' (with the attribute 'Rcvd' set in their header)
so you will be able to read them anytime but, after you have checked the
already processed request, you must delete them manually. For our tuto-
rial leave this toggle to "N" status.
5.5.6.7 - Keep receipts
The receipts are the "return NetMail messages" that AreaFix gene-
rates when it processes any AreaFix request from your downlinks telling
him what action was performed. These receipts are, normally, marked with
the 'Kill/Sent' attributes and, thus, deleted after being sent back to
your downlinks; so you cannot check them. If, on the other hand, you
need to check these receipts before they are deleted, you can enable
this feature by toggling it to "Y" but, after being checked, you must
delete them manually, of course. For our tutorial leave this feature
disabled (in "N" status).
5.5.6.8 - Scan before tossing
By default, the FastEcho TOSS function (we shall see it later in
"Using FastEcho" section)processes the AreaFix requests just after all
incoming mail has been tossed. If you enable this feature, FastEcho will
scan the primary NetMail area (The one commonly defined between Fast-
Echo and you Mailer; see also 5.4.4.1 chapter) just before starting to
process the incoming ARCmail packets. This behavior will make it possi-
ble for the changes requested in the AreaFix messages will immediately
apply upon the incoming mail.
5.5.6.9 - Detailed List
As we said before (see paragraph 5.5.5.1.7), the FastEcho's AreaFix
processor has the power to generate return-reports containing a list of
all the areas available to the downlink that sent the MetaCommand %LIST
to your system, in an AreaFix request. This areas-list, normally, is a
list of the area's "EchoTag" without any description. By enabling this
option, you could give a better service to your downlinks providing a
more meaningful area list report. The list report generated when this
function works, in fact, will contain all the EchoTags with their re-
spective description (the one that you inserted in the "Comment" field
when you defined every EchoMail areas. See chapter 5.5.3.1.3). For our
tutorial toggle this option to "Y" status.
5.5.6.10 - Add list to receipt
With this option enabled, FastEcho AreaFix will always add a list of
all active areas in every report it generates for the downlinks that re-
quested them. For our tutorial leave this toggle disabled.
───────────────────────────────────────────────────────────────────────
- 100 -
FastEcho MANUAL - Tutorial - Data dropdown menu - AreaFix Options -
───────────────────────────────────────────────────────────────────────
5.5.6.11 - Password in &INFO
This option is intended to allow or deny FastEcho AreaFix to include
the User AreaFix password and packet password in the NetMail receipt
automatically generated after a remote request has been processed. Note
that both these password must normally remain private and reserved,
thus, before enabling this function, take care to check that NetMail
messages containing password won't be routed.
5.5.6.12 - Send conference rules
As already seen in the paragraph 5.5.1.18.3, FastEcho AreaFix is
capable to automatically send to your downlinks the conference rules
(area policies) of every new echomail area they want to be linked via
an AreaFix request. To do that you must have, of course, the conference
rules of all echomail areas you actually have available on your system.
When enabled, this option bind FastEcho to always send the conference
rule whenever a system request a new echomail area, otherwise, when the
switch is set to "No", the "Send conference rules" function is globally
disabled. Note that, in order to let FastEcho to work correctly with
your rule-files, you must also define the location in where these rule
file are kept (Look at the chapter PathNames 5.4.4)
5.5.6.12.1 - Rulefile area tag prefix
If you have enabled the "Send conference rules" option seen in the
previous paragraph, then you must define the "Rulefile area tag prefix"
you adopted for your rule files. These prefix identifies the echotag of
the area to which these rules belongs. The rule files are plain text
files containing a somewhat standardized header before the conference
rule list. The first line of this special header must contain the area
tag prefix. The area tag prefix most commonly used are Area :<areatag>
or EchoID :<areatag>.
Example: RuleFile for area FASTECHO.ITA (this file is named FEITA.RUL)
Area : FASTECHO.ITA
Description : Technical conference about FastEcho
Language : Italian/English
Moderator : Marco Piazza, 2:331/501.25
Rulefile : FEITA.RUL
Permission : All
Date : 25.03.1997
-----------------------------------------------------------------
<Rules follow>
In this case the rulefile areatag prefix you must define in this item
will be
Area :
which is also the standard that FastEcho assumes as default (i.e.
will be taken as default if this field is left empty). If Other country
has different standard prefixes then take care to insert the right
prefix exactly as is in your header files, including spaces and trailing
separators, otherwise FastEcho won't parse them.
───────────────────────────────────────────────────────────────────────
- 101 -
FastEcho MANUAL - Tutorial - Data dropdown menu - AreaFix Options -
───────────────────────────────────────────────────────────────────────
5.5.6.13 - Max. receipt size
There are some mail processors unable to handle NetMail messges lar-
ger than 8-16 kilobytes, while, certain AreaFix receipts messages can go
beyond this limit (this could happen, for example, when requesting an
AreaFix %LIST MetaCommand on a system having an enormous quantity of
EchoMail areas available, and that's not so uncommon indeed). By means
of this option you can solve this problem by fixing the maximum size of
an AreaFix receipt within a certain size. If it happens that the receipt
goes over the limit specified in this option, then it will be split into
smaller pieces. For our tutorial leave this field zero.
5.5.6.14 - AreaFix %HELP File
As said before in chapter 5.5.5.1.20, when a downlink send an Area-
Fix request having in its text the MetaCommand %HELP, then the AreaFix
processor provides him a receipt containing a summarized list of all the
AreaFix metacommands. The default AreaFix help file included in the
FastEcho distribution archive is "AreaFix.HLP" but, by means of this
option you now have the choice to customize this file by creating seve-
ral AreaFix help-file accordingly with your needs (translated in your
preferred language or containing more detailed informations). Striking
the "return" key over this item, the following box will be shown to you:
╔═══════════════════ AreaFix-Helpfile ════════════════════╗
║ AreaFix.HLP_ ║
╚═════════════════════════════════════════════════════════╝
All you need is to specify in this field the file name of your pre-
ferred AreaFix help-file. For our tutorial leave in this box the default
specification for AreaFix.HLP.
5.5.6.15 - Forward Requests
We have talked several times, throughout this manual, about the For-
ward AreaFix Request feature, especially in the 5.5.1.9 and paragraph
5.5.4.1.14. But, what is it really is and how does it works? Well, As
you certainly already know, a downlink can join new EchoMail areas
available on your system simply by sending you an AreaFix link request
(see the relative option in paragraph 5.5.5.1.1) and that's quite normal
but, how about leaving to your downlinks the option to link themselves
to areas that you HAVEN'T yet available on your system but your uplink
has?? This can be done through the use of the Forward AreaFix Request
feature. To enable this option, first, you must obtain, from each of
your uplinks, a file containing the list of areas currently imported by
them and define them in the section we shall see later (these lists can
be in the standard "AREAS.BBS" format or in a kind of User definable
format that we shall treat later), furthermore, you must be registered,
otherwise you can only define one area list. Until now, for the samples
reported in the manual, Now, furthermore, I assume that your system has
two uplinks, one for Fidonet (2:999/900) and one for ZyXELnet
(16:999/900). I assume that you have got from these two downlinks their
imported areas list in two "AREAS.BBS" standard files named:
FIDAREAS.TXT and ZYXAREAS.TXT. Now let's go to the setup details.
Placing the cursor upon the "Forward Request" item and striking the
return key you will have access to the Forward Request settings by means
of this first layout that will be displayed on your screen:
───────────────────────────────────────────────────────────────────────
- 102 -
FastEcho MANUAL - Tutorial - Data dropdown menu - AreaFix Options -
───────────────────────────────────────────────────────────────────────
╔═════════════════════ Forward AreaFix-Requests ═════════════════════╗
║ Forward to List file Remote program Active ║
║────────────────────┬─────────────────────┬─────────────────┬───────║
║ A) │ │ │ ║
║ B) │ │ │ ║
║ C) │ │ │ ║
║ D) │ │ │ ║
[...] │ │ │ [...]
║ T) │ │ │ ║
╚════════════════════════════════════════════════════════════════════╝
Enter-Edit F2-Active F3-Move Del-Kill list entry
The screen layout is subdivided into four columns and twenty rows.
Let's see what the column items means:
5.5.6.15.1 - Forward to
In this column will be listed the systems to which the AreaFix re-
quests will be forwarded, according to their akas
5.5.6.15.2 - List file
Here will be displayed the path and file name containing the Echo-
Mail area list, available from the system reported under the "Forward
to" column on the same row.
5.5.6.15.2 - Area Manager
Herein will be listed the kind of Area Processor owned by the uplink
system displayed under the "Forward to" column on the same row. When the
AreaFix Request is forwarded, then, it will be addressed to the Area
Processor specified in this slot.
5.5.6.15.3 - Active
This column will be displayed if the Forward AreaFix Request feature
is active or not for the system specified on the same row. This option
provides the convenience to disable temporarily the Forward AreaFix re-
quest to one or more systems without removing them, thus, you will save
time to by not inserting again all the necessary parameters once you ha-
ve decided to re-enable them. This could be done simply by toggling the
in the "Active" column "Yes" or "No" according to your needs.
5.5.6.15.4 - Setting up Forward AreaFix Requests
When you are ready to start the configuration of the first system to
which you want FastEcho to automatically forward the AreaFix link re-
quest, simply press the return key. You will immediately see that the
following layout pops up:
───────────────────────────────────────────────────────────────────────
- 103 -
FastEcho MANUAL - Tutorial - Data dropdown menu - AreaFix Options -
───────────────────────────────────────────────────────────────────────
╔═══════════════════════ Forward requests to ═══════════════════════╗
║ ┌─────────────┐ ║
║ Forward:│>2:999/900< │ Unconditional: N ║
║ │ 2:999/999.1 │ ║
║ List file:│ 16:999/900 │ ║
║ └─────────────┘ ║
║ List type: Remote program: ║
║ ║
║ Deny list: ║
║ ║
║ Groups: ABCDEFGHIJKLMNOPQRSTUVWXYZ123456 Security: ║
║ ║
║ Add '+': N Add '---': Y New Area Default Group: A ║
║ ║
║ Create as passthrough: Y ║
║ ║
╚═══════════════════════════════════════════════════════════════════╝
5.5.6.15.4.1 - Forward
The first thing you will immediately be prompted to select is the
uplink address, to which you want that FastEcho to forwards the AreaFix
requests for the EchoMail areas contained in the Area List file (that we
shall see later). Your choice can be made by means of a selection box
that lists, inside, all your configured system. (be aware that, not all
your configured systems may be uplinks. With all probabilities you will
setup both uplinks and downlinks so, although in this box both of them
will be listed , make sure to select only the uplinks). The selection
will be done by moving, in the usual way, the highlighted box over the
uplink's address you need, and striking the "return" key to confirm.
Immediately, in the "Uplink" slot, will appear the selected address and
you will be prompted to input the next item. For our tutorial place the
pointer over the "2:999/900" address and strike return.
5.5.6.15.4.2 - Unconditional
As you already know, the "Forward AreaFix Request" functionality is
normally based, firstly, upon the EchoMail areas listed in the related
file defined in the "Area List" item, and, further, upon the security
level and the allowed groups matching. If you toggle this "Unconditio-
nal" feature to "Y" status, then the AreaFix Request will be forwarded
to this uplink even if the requested EchoMail areas aren't reported in
the "Area List" file, so the "Area List" field could remain undefined
too. When the "Unconditional" option is turned on, the requests for all
areas will be "unconditionally" forwarded to the uplink defined in the
item 5.5.6.15.5.1. The only things that must match, in all case, will
remain the security level and the allowed groups you will fix for this
Uplink. For our tutorial leave this option disabled.
5.5.6.15.4.3 - Area List
This is a free field where you can input the path and file name of
your file, containing the areas available from your uplink. Make sure to
define herein the file containing the EchoMail areas available from the
uplink specified in the paragraph 5.5.6.15.5.1.
───────────────────────────────────────────────────────────────────────
- 104 -
FastEcho MANUAL - Tutorial - Data dropdown menu - AreaFix Options -
───────────────────────────────────────────────────────────────────────
5.5.6.15.4.4 - List Type
In this field you must specify the type of the EchoMail area list
contained in the file defined in the previous item (5.5.6.14.5.3). Cur-
rently, FastEcho supports two formats for this file: the first is the
AREAS.BBS standard type and the second is a more flexible format that
could be used if the AREAS.BBS type isn't available; this last one could
be an area list generated by your uplink with almost any EchoMail pro-
cessor or external utilities as well. The AREAS.BBS listing type has the
following format:
<board or pathnames> <EchoTag> <connected system's addresses>
In this case FastEcho ignores the <board or pathnames> and the <connec-
ted system's addresses> parameters keeping into due consideration the
EchoTag only. So it doesn't matter if your uplink uses HMB, Squish, JAM
or *.MSG mail processor. The free format is, instead, interpreted by
FastEcho in the following format:
<EchoTag> <Description>
In this case both, EchoTag and Description will be used. Only the
Echotag parameter is mandatory but, furthermore, if the <Description>
item is found, then, its contents will be automatically inserted in
FastEcho setup into the Area Comment item (see: paragraph 5.5.3.1.3). In
order to select the 'Type' you prefer, you will be prompted to choose by
means of the following box:
┌──────────────────────┐
List type: │>AREAS.BBS< │
│ <name> <description> │
└──────────────────────┘
Simply place the highlighted box over the 'Type' you need and strike
return. For our tutorial select the AREAS.BBS type and go ahead.
5.5.6.15.4.5 - Remote program
Here you must choose between four different Area-Manager names. When
the cursor will be placed over the Area-Manager item, then, automati-
cally the following dialog box will be shown on your screen:
┌──────────┐
Area Manager:│>AreaFix< │
│ AreaMgr │
│ AreaLink │
│ EchoMgr │
└──────────┘
We have seen, in the chapter 5.5.5.1.1, that an AreaFix request is a
normal NetMail message addressed to an Area Manager's name that, usual-
ly, is 'AreaFix'. But someprocessors need a different name from AreaFix
even if almost all processors nowadays accept it. In any case, if you
meet some problems with your uplink (I.E. AreaFix requests not honored),
then change this Area Manager's name with the one needed from the area
manager used by your uplink. For our tutorial, the better choice is the
'AreaFix' name, so place the pointer over this item and strike return.
───────────────────────────────────────────────────────────────────────
- 105 -
FastEcho MANUAL - Tutorial - Data dropdown menu - AreaFix Options -
───────────────────────────────────────────────────────────────────────
5.5.6.15.4.6 - Deny list
In this field can be specified the name of a file which contains the
tag of the areas you don't want be forwarded even if found in the used
list file (defined in the "list-type" item seen in the paragraph
5.5.6.15.4.4). This file must contain an areatag list (one tag each
line) and each tag may also be written with wildcard carachters ("*" and
"?"). As deny list file may further be defined an Echolist style file
too. In this case only the echotag entries will be parsed while the area
desciption will be ignored at all.
5.5.6.15.4.7 - Groups
In order to allow FastEcho to process the 'Forward AreaFix Request'
requested from your downlinks, there are, first, two condition that must
be satisfied. The present is the first: The area requested from your
downlinks must belong to a group defined by way of this option. To se-
lect the allowed groups you will have to tag them in the following dia-
log box that will be shown to you:
╔═══════════════════════ Forward re┌────────────────────────────────┐
║ │■ A) Fidonet EchoMail area Intl │
║ Uplink: 2:999/900 │■ B) Fidonet EchoMail area Natl │
║ │ C) ZyXELnet EchoMail area │
║ Area List: C:\FAST\FIDAREA.TXT │ D) Local BBS area │
║ │ E) NetMail area │
║ List type: AREAS.BBS │ F) │
║ │ G) │
║ Groups: │ H) │
║ │ I) │
║ Add '+': N Add '---': N New A[...] [...]
║ │ Z) │
╚══════════════════════════════════└────────────────────────────────┘
The selection of a group can be done simply by moving the pointer
with the arrow-keys and tagging the groups you want by pressing space.
Any tagged area will be immediately identified by way of the little
black box, that marks them, shown to their left. Remember to select the
groups according to the uplink type. (I.E. If you allow one or more
ZyXELnet EchoMail groups while configuring a FidoNet Uplink may be
wrong). When finished press the return key to confirm your selection and
continue. You will see the letter that identifies your selected groups,
displayed in the 'Groups:' item. For our tutorial tag the group A) and
B) relative to the Fidonet Uplink.
───────────────────────────────────────────────────────────────────────
- 106 -
FastEcho MANUAL - Tutorial - Data dropdown menu - AreaFix Options -
───────────────────────────────────────────────────────────────────────
5.5.6.15.4.8 - Security
As mentioned in the previous item, this is the second condition that
must be satisfied before the requesting node is able to perform a 'For-
ward AreaFix Request' action. In this field you may input the minimum
security level that a downlink must have to be allowed to perform a
'Forward AreaFix Request' to the uplink defined in the Uplink item (see
paragraph 5.5.6.14.5.1).If the security level of the requesting downlink
is greater or, at least, equal to the level specified in this Security
item,then the AreaFix Request will be forwarded, otherwise the automatic
forward operation will be denied and the downlink request discarded. For
our tutorial input in this field the value 100.
5.5.6.15.4.9 - Add '+'
We have seen, talking about adding new area through AreaFix, in the
paragraph 5.5.5.1.1, that, linking a new area can be done simply by spe-
cifing the EchoTag of the necessary area in the text of an AreaFix re-
qeust but, some processors, in order to work correctly, need the plus
sign preceeding the EchoTag of the requested area. So, by taking this
option, you can make FastEcho to add the plus sign before any automatic
requested area, thus,solving the problem. For our tutorial leave this
option disabled.
5.5.6.15.4.10 - Add '---'
The triple dash represents the mandatory part of the tearline (See:
5.4.7.1 and 5.4.7.2). An AreaFix request, normally, doesn't need it, so
,by default, FastEcho doesn't insert it at the end of its own automati-
cally created message. Nevertheless, some older processors need it to be
able to work correctly, so, by means of this clause, you can solve this
problem by making FastEcho insert it all the same. For our tutorial
leave this option disabled.
5.5.6.15.4.10 - New Area Default Group
Last of all, FastEcho has to know to which group the new EchoMail
area, that your uplink will start to send you after having processed
your AreaFix request, will belong to. So you can define the groups, when
the cursor will fall into this item, FastEcho will show an ulterior
dialog box:
╔═══════════════════════ Forward re┌───────────────────────────────┐
║ │>A) Fidonet EchoMail area Intl<│
║ Uplink: 2:999/900 │ B) Fidonet EchoMail area Natl │
║ │ C) ZyXELnet EchoMail area │
║ Area List: C:\FAST\FIDAREA.TXT │ D) Local BBS area │
║ │ E) NetMail area │
║ List type: AREAS.BBS │ F) │
║ │ G) │
║ Groups: AB │ H) │
║ │ I) │
║ Add '+': N Add '---': N New A[...] [...]
║ │ Z) │
╚══════════════════════════════════└───────────────────────────────┘
───────────────────────────────────────────────────────────────────────
- 107 -
FastEcho MANUAL - Tutorial - Data dropdown menu - AreaFix Options -
───────────────────────────────────────────────────────────────────────
Simply select, in the usual way, the group that fits the EchoMail
area requirements better. FastEcho needs to know that because, when it
starts to receive the new area from your downlink, it has to know which
area-default must be taken over to automatically configure it. When you
selected the right group, confirm your selection with the return key;
You will see, once again, the dialog box we saw at the beginning of this
chapter, don't worry, press return again until the cursor is placed in-
side the Uplink field. At this point strike F10 to save your entry. For
our tutorial place the highlighted box over group B), strike return
twice and then the F10 Key.
5.5.6.15.4.11 - Create as passthrough
When this switch is enable (toggled to 'Yes') then all areas created
by mean of the Forward Areafix Request function will automatically
created as passthrough even if the "storage" setting in your "Group
area default" is differently specified. Is adviceable to leave this flag
enabled because if your downlinks request a lot of areas you may easily
run out of diskspace. Further, remember that the "Automatic passive"
function (see paragraph 5.5.1.22) works only upon passthrough areas.
.-.-.
Here you have finished the dressing of the 'Forward AreaFix Request'
layout, enabling this feature for the first uplink. Your 'Forward Re-
quest' main layout should now look like the following:
╔═════════════════════ Forward AreaFix-Requests ═════════════════════╗
║ Forward to Area List Area Manager Active ║
║────────────────────┬─────────────────────┬─────────────────┬───────║
║ A) 2:999/900 │ C:\FAST\FIDAREA.TXT │ AreaFix │ Yes ║
║ B) │ │ │ ║
║ C) │ │ │ ║
║ D) │ │ │ ║
[...] │ │ │ [...]
║ T) │ │ │ ║
╚════════════════════════════════════════════════════════════════════╝
Enter-Edit F2-Active F3-Move Del-Kill list entry
Now you may repeat the operation from 5.5.6.13 until 5.5.6.14.10 for
all your uplinks (changing the necessary data, of course). For our tuto-
rial define the 16:999/000 uplink too.
.-.-.
Here you have also completed the Data DropDown Menu setup and, thus,
also the main settings of your FastEcho core. Now it's time to start
learning the pratical use of the FastEcho program and the FEUTIL compa-
nion utility. Exit now from the Forward-Arefix-Request layout by
pressing the ESC key; then exit from the Data-DropDown-Menu by pressing
ESC again. You have now returned to FastEcho Main Screen.
───────────────────────────────────────────────────────────────────────
- 108 -
FastEcho MANUAL - Tutorial - Data dropdown menu - AreaFix Options -
───────────────────────────────────────────────────────────────────────
5.6 - Export DropDown Menu
====================
This is a utility that allows you to export your area configuration
into three different files. Each one has its purpose.
FESetup System Data Export Import F1 Help
░░░░░░░░░░░░░░░░░░░░░░░░░░░░░┌──────────────┐░░░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░░░░░░░░░░░░░░░░░│>AREAS.BBS< │░░░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░░░░░░░░░░░░░░░░░│ SQUISH.CFG │░░░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░░░░░░░░░░░░░░░░░│ Echolist │░░░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░░░░░░░░░░░░░░░░░│ ASCII.file │░░░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░░░░░░░░░░░░░░░░░│ ROUTE.file │░░░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░░░░░░░░░░░░░░░░░└──────────────┘░░░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
Create AREAS.BBS file from area database
5.6.1 - Export AREAS.BBS
----------------
The AREAS.BBS file is a standard, human readable, file containing
all the areas that your system has already configured, each one with its
EchoTag and the connected systems, if any. By means of this file, is is
often possible to exchange information about connected EchoMail areas
between different mail processors; furthermore, many mail editors
support it in order to automatically configure themselves in accordance
with your current EchoMail configuration. Moreover, as mentioned in
chapter 5.5.6.14.5.4, it could be useful for your downlinks to let them
use the 'Forward AreaFix Request' feature on their systems.
5.6.2 - Export SQUISH.CFG
-----------------
This function will become useful if you need to export a SQUISH.CFG
compatible configuration file you can use in order to save time when
installing or modifying your squish system.
5.6.3 - Export Echolist
---------------
This option allow you to export an ascii file which contains a list
of all areas with all their descriptions exactly as you configured them
in Area Manager This file is FIDONET.NA compatible.
5.6.4 - Export ASCII file
-----------------
The so called ASCII file represents a human readable file that con-
tains the complete descriptive configuration of your FastEcho. Pratical-
ly it completely contains all settings you made in FESetup. It can be
useful you in order to check all your current configurations at a
glance.
───────────────────────────────────────────────────────────────────────
- 109 -
FastEcho MANUAL - Tutorial - Data dropdown menu - AreaFix Options -
───────────────────────────────────────────────────────────────────────
5.6.5 - Export ROUTE.FE
---------------
It may be helpful to export this ROUTE file in case you wish to use
the automatic FastEcho packer/router. As we shall see later, FastEcho
has an high performance NetMail packer/router built in, that can be used
in two ways:
'FASTECHO PACK <address,address,...> via <address>'
or, better, through the
'FASTECHO PACK -F<route file>'
(We shall see its exact use in the proper paragraph ). The <route
file> parameters could be replaced with the file-name containing the
routing statements for every node configured in your node manager (see:
5.5.1.24.2) that may be created by means of this export function.
5.7 - Import DropDown Menu
====================
From the Main FESetup screen, place the highlighted box over the
'Import' item and strike the return key; you will be able to access the
the import feature by using the following dropdown menu:
FESetup System Data Export Import F1 Help
░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░┌─────────────┐░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░│ Echolist │░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░│─────────────│░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░│>AREAS.BBS< │░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░│ SQUISH.CFG │░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░│ IMAIL.ND │░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░│ IMAIL.AR │░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░│ NODEFILE.FD │░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░│ AREAFILE.FD │░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░│ NODEFILE.GE │░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░│ AREAFILE.GE │░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░░░░░░░░░░░ FastEcho;│ FMAIL.NOD │░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░│ FMAIL.AR │░░░░░░░░░░░░░░░░░░░░░░
░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░│ XMAIL Files │░░░░░░░░░░░░░░░░░░░░░░
░░░░ Copyright 1991-97 by Softwar└─────────────┘ rights reserved. ░░░░
░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
Import an AREAS.BBS area file
───────────────────────────────────────────────────────────────────────
- 110 -
FastEcho MANUAL - Using FastEcho -
───────────────────────────────────────────────────────────────────────
This section could be very useful if you plan to upgrade to
FastEcho while, before, you used mail processors like Tosscan, IMail,
GEcho and so on. All you need is a copy of your AREAS.BBS file from
your old mail processor and, let the FastEcho import feature translate
it to a new FastEcho configuration. The imported configuration, of
course, will need, however,some little additional touch in order to
fine-tune it but, I don't think, it will be hard for you. If you don't
have the AREAS.BBS available, don't worry, you will be able to import
several other proprietary configuration formats for IMail, FMail,
TosScan and GEcho; furthermore, you have the choice to import the, so
called, EchoList file; that's a somewhat standard FidoNet file called
FIDONET.NA, which contains the description of the EchoMail areas in the
format
<EchoTag> <Description>.
While importing this file, FastEcho updates, after your confirma-
tion, the area descriptions of the areas already configured in "Node
Manager" by inserting the right description or repalcing an existent
one into the "Comment" field (see chapter 5.5.3.1.3).
.-.-.
Here you really have finished discovering FESetup: The FastEcho in-
teractive configuration utility. In the next chapter we shall begin
using the FastEcho mail processor. If you have followed the tutorial
until now and have read carefully all the FESetup options, now you know
how to change all the inserted parameters yourself, according to your,
uplinks and downlinks necessities. When you have finished your real
configuration then remember to double check it both, directly and by
exporting your settings, relying upon the FastEcho capability seen in
the paragraph 5.6.2. When you think that's all right then follow onto
the next chapter.
6 - USING FastEcho
==============
Here we shall start to use the FastEcho main program in order to
process your outgoing and incoming mail. I assume that, before start
this section, you have already followed chapter 5, where we pointed out
all the necessary operations to correctly set up the parameters needed
to let FastEcho work correctly.
6.1 - Help on line
------------
Before checking the FastEcho functionalities, it would be better
try executing it without any parameter. In this case, FastEcho will
give you a summary of the functions that it mainly performs. From the
DOS prompt input "FastEcho" followed by the return key. You will see
the help screen shown here below:
───────────────────────────────────────────────────────────────────────
- 111 -
FastEcho MANUAL - Using FastEcho -
───────────────────────────────────────────────────────────────────────
----------------------------------------------------------------------
Usage:
FastEcho TOSS [-B][-C][-F][-S] - Toss inbound mail
FastEcho SCAN [-N][-A][-F][-I][-L<file>] - Scan for outbound mail
FastEcho PACK [-I][-F][-P][Adr...[via Adr]] - Pack outbound NetMail
or [-R<file>]
FastEcho AFIX [-F] - Scan for AreaFix-request
FastEcho NOTIFY [Adr [Adr] ...] - Send AreaFix notify messages
FastEcho HELP [Adr [Adr] ...] - Send AreaFix help messages
FastEcho RELINK [Adr [Adr] ...] - Send AreaFix relink messages
FastEcho STAT[-R[S]][-G<g>][-O][-H][-N] - Generate mail statistics
Call 'FastEcho <command> ?' for more detailed help ...
----------------------------------------------------------------------
As you can see, this main Help-Screen summarizes all the available
FastEcho commands andeachwith the available options and switches. You
can also rely upon more detailed help screen, over about all options
and all switches, by simply executing them with the trailing question
mark, for example, if you need further information about the "FastEcho
TOSS" function then you can input:
FastEcho TOSS ? (Or FastEcho TOSS /?)
from the DOS prompt, obtaining the second level help screen:
----------------------------------------------------------------------
FastEcho TOSS [-B] [-C] [-F] [-S] - process inbound mail
<switches>
-B : retoss messages from BadMail area
-C : make Carbon-copies of imported mails
-S : disable all Security-checks
-F : don't create a File-attach(es)
----------------------------------------------------------------------
in which is explained, in detail, what every switch does.
6.2 - FastEcho Toss
-------------
The "TOSS" operation must be performed in order to process the in-
coming mail packets. As you already know, the incoming mail packets are
stored by your Mailer in the "Inbound" directory when they are received
from your links. They are initially in an archived form (compressed),
so they need to be unarchived before they can be processed (See
5.4.4.3, 5.4.4.4, 5.4.11). When the FastEcho Toss command is executed,
FastEcho automatically checks in the inbound directory if new ARCmail
bundles exist and, if so, it starts to unarchive the found ARCmail
bundles containing one or more mail packets; furthermore, it starts to
process the mail packets by scanning them in order to detect, and con-
textually extract, all the contained messages and, finally, distribu-
ting the messages in your configured EchoMail Areas according to their
───────────────────────────────────────────────────────────────────────
- 112 -
FastEcho MANUAL - Using FastEcho -
───────────────────────────────────────────────────────────────────────
EchoTag (Area Name). During the tossing operation "FastEcho Toss"
automatically checks if you received mail belonging to areas which your
downlinks are connected to and, if so, it starts forwarding their mails
by creating new mail packets and when finished archiving them in
ARCmail bundles, storing these ARCmail bundles in the OUTBOUND
directory and addressing them to your downlinks by means of appropriate
file-attaches created in the "primary NetMail area" (as we have seen
in chapter 5.4.4.6). Moreover, the "TOSS" operation, after having per-
formed the aforesaid function, starts to check if, in the "Primary Net-
Mail Area", any AreaFix requests exist, and, if so, it automatically
executes the built-in FastEcho AreaFix function in order to process
them. Remember that FastEcho toss ignores all PKTs having the "read-on-
ly" flag set. The "TOSS" function can be formulated with four variants
in the form of commandline switches. Let's see them in detail.
6.2.1 - FastEcho Toss -B
We have talked about BadMail several times throughout this manual
(look at chapters 5.4.7.4, 5.5.2.3, 5.5.2.5 and 5.5.3.1.1) so you are
now sufficiently aware of it, I think. You know that, when your uplink
starts to send you, for example, an EchoMail area that you haven't pre-
viously requested and you haven't got the FastEcho "Auto Area Create"
feature active for this node in your configuration, then, FastEcho will
toss all the EchoMails belonging to this undefined area directly in
your BadMail area. If after having checked the received bad EchoMail,
you decide to switch this area active on your system, configuring it
with FESetup, then you need to pour off all your previous bad messages
in the proper new area you have just created. In this case the switch
we are using now may help. By executing the command:
FastEcho TOSS -B
from the DOS prompt, in fact, all the messages contained in the BadMail
area will be completely re-scanned, re-tossed and thus, re-distributed
in the proper areas (if you have meanwhile created them).
6.2.2 - FastEcho Toss -C
To explain this switch I need to remind you of the chapter 5.5.4,
where we extensively talked about the Carbon Copies and their means. In
the aforesaid chapter, as a matter of fact, we set up the Carbon Copy
function to make its work possible. The Carbon Copy function, in brief,
intervenes while FastEcho tosses the mail packets in order to detect
among them, the ones which you are interested in. FastEcho, of course,
knows which are the messages you want to duplicate thanks to your set-
ting tuned in chapter 5.5.4. If you want to activate the Carbon Copy
function you need to invoke the TOSS operation adding the "-C" switch:
FastEcho TOSS -C
Remember that without the "-C" switch this function won't be active,
although your settings in 5.5.4 section have been done correctly and
remember also that the carbon-copy system ignores completely all the
messages tossed in your badmail area.
───────────────────────────────────────────────────────────────────────
- 113 -
FastEcho MANUAL - Using FastEcho -
───────────────────────────────────────────────────────────────────────
6.2.3 - FastEcho Toss -S
We have seen in chapters 5.4.7.14, 5.5.1.5.1, 5.5.1.5.2, 5.5.1.8,
and in several other chapters, how many security features FastEcho has.
That's not bad indeed, but in some cases you may want to temporarily
disable all the security functions provided by FastEcho. This can be
done simply by invoking the FastEcho TOSS function with the -S switch:
FastEcho TOSS -S
Avoid the insertion of this switch in your permanent batch-file be-
cause it's absolutely unadvisable to leave the security functions disa-
bled permanently.
6.2.4 - FastEcho Toss -F
When invoked with the -F Switch, FastEcho "TOSS" starts its normal
procedures, processing the incoming mail bundles, exactly as explained
in the paragraph 6.2 at the beginning of the present section but, when
it finishes forwarding mail to your downlinks, by creating the appro-
priate ARCmail bundles, it avoids the generation of the necessary file
attaches in the "primary NetMail area". Be aware that, doing so, your
downlinks won't be able to pick up their mail, although it may be pre-
sent. That's because, when the mailer answers their calls it won't be
aware of any mail being sent due to lack of necessary NetMail attaches
references. Use this switch only if you really need it (I.E. when wor-
king in LAN environment) and only if you are perfectly aware of what
you are doing.
6.3 - FastEcho Scan
-------------
The "SCAN" operation must be performed whenever you want FastEcho
to scan your local messagebase(s) in order to find new messages to be
sent. The local messages are the ones that may be locally inserted both
by you (by means of a messagebase editor) and by the interactive users
of your Bulletin Board System. For example: If you insert an EchoMail
message locally, by means of your preferred messagebase editor, it will
be stored in the corresponding local messagebase with the attribute
"Uns" that means "Unsent"; to allow this message to be sent, then
FastEcho has to scan this messagebase; when this new message is found,
then FastEcho will mark it as "Snt" within the messagebase and, it
exports the message contents out of the messagebase and stores it into
new mail packets. Furthermore FastEcho will archive these mail packets
producing an ARCmail bundle, storing it in the OUTBOUND directory, and,
finally, it creates the "File attach" for this new bundle so that your
mailer can be aware that there is new mail to send (or to be picked
up). This speech is valid also if there is more than one EchoMail
message to be sent, of course, and FastEcho, thanks to its swiftness,
can perform the scan operation in one single pass, independently from
the number of messages to be sent existing in your messagebases. The
only exception to this mechanism happens when you insert a new NetMail
message in your "Secondary NetMail Area" (as you certainly remember
there are some substantial differences between Primary and Secondary
NetMail areas (See, for references,chapters 5.4.4.1 and 5.4.14.1.2).
When performing the "SCAN" operation, if FastEcho detects one or more
NetMail messages marked with the "Unsent" flag in your "Secondary
───────────────────────────────────────────────────────────────────────
- 114 -
FastEcho MANUAL - Using FastEcho -
───────────────────────────────────────────────────────────────────────
NetMail Area", it will export them, as usual, but, instead of inserting
them in a mail packet (as instead happens for the EchoMail messages, as
we have seen before), they will be merely exported from your
"Secondary NetMail Area" into your "Primary NetMail Area" as *.MSG,
leaving them there for further processing or to be directly routed
through your mailer (remember that the "Primary NetMail Area" is shared
between FastEcho and your Mailer). To increase the performances,
FastEcho uses some files that your BBS software and your messagebase
editor creates when you insert new EchoMail or NetMail messages in your
messagebase. These files are named ECHOMAIL.BBS, NETMAIL.BBS,
ECHOMAIL.JAM, NETMAIL.JAM. The two having ".BBS" extension are used for
the Hudson Message Base while the other two are used for the JAM
messagebase. But, what do these files really contain? They contain the
exact location of the newly inserted message in EchoMail (EchoMail.BBS
or EchoMail.JAM) and in NetMail (NetMail.BBS or NetMail.JAM), if at
all, within your messagebases (both JAM or HMB). When a "SCAN"
operation is performed, then FastEcho immediately looks for these files
and, if they exists, FastEcho will look inside them to see if there are
new message and where to find them exactly, avoiding, so, to rescan the
whole messagebase contents, so saving a lot of time.
The "SCAN" function can be formulated with four variants in the
form of commandline switches. Let's see them in detail.
6.3.1 - FastEcho Scan -N
As we said in the previous chapter, FastEcho makes use of EchoMail
and NetMail.BBS, EchoMail and NetMail.JAM to speed up its overall per-
formances but, in some cases, this could be unwanted (I.E. it may hap-
pen that your preferred messagebase editor doesn't update these files
while, instead, your BBS does it. So,while FastEcho performs the "SCAN"
operation it may find the NetMail/EchoMail.BBS/JAM, created by your BBS
software, containing the references of EchoMail and NetMail messages
inserted by the interactive users of your BBS, but not yours. The re-
sult will be that your locally inserted messages will never be sent.
Only if you come across this problem use the "-N" switch) If you use
the "-N" switch, then, the scanning operation will involve the whole
messagebase with no regards to any of the aforesaid files.
6.3.2 - FastEcho Scan -A
As opposed to the previous one, this switch will bind FastEcho to
perform the "SCAN" operation only if it is able to find the EchoMail
and NetMail.BBS, EchoMail and NetMail.JAM files (Refer to the main
FastEcho Scan chapter: 6.3, for details about the meaning of these
files.) otherwise the FastEcho "SCAN" execution will abort.
───────────────────────────────────────────────────────────────────────
- 115 -
FastEcho MANUAL - Using FastEcho -
───────────────────────────────────────────────────────────────────────
6.3.3 - FastEcho Scan -F
We already seen, in the chapter 6.3, how the "SCAN" mechanism
works. Well, when you invoke the "SCAN" function with this additional
switch, the operation performed by FastEcho will be exactly the same as
we have seen in the chapter 6.3 with the only exception that, after the
ARCmail bundles, containing the outgoing mail packets, are created in
the OUTBOUND directory, FastEcho won't generate the necessaryARCmail
attaches in the "Primary NetMail Area". take note that, normally, in
this way, your mailer won't be aware of the ready-to-be-sent ARCmail
bundles, wich means they will never be sent nor picked up to/from any-
one although they effectively exists. Use this switch only If you
really need it, for example, when working in LAN environments.
6.3.4 - FastEcho Scan -I
FastEcho, in order to increase its high speed while scanning JAM,
Squish and *.MSG messagebases, can make use, and update too, the so
called HighWaterMarks. When FastEcho performs the "SCAN" operation upon
JAM, SQUISH and *.MSG messagebases, in fact, thanks to the
HighWaterMarks system, it can keep track of the last message which has
been processed in a previous scanning, so, if not otherwise specified,
it will check only the newer messages (having higher message numbers)
starting the scan operation directly from the address pointed by the
HighWaterMarks, instead of scanning the whole message base, saving, in
this way, a lot of precious time that could be spent otherwise.
Nevertheless, it could happen that, some old messagebase editors don't
set these "marks" correctly. in this case the -I switch could be
helpful. If you specify the "-I", infact, FastEcho will ignore the
HighWaterMarks index completely, so, the whole messagebase will be
scanned from the beginning to end.
6.3.5 - FastEcho Scan -L<file>
This switch is strictly related to the Squish and Old-Fido-Style
*.MSG messagebases; in fact it works only with them and doesn't work
with HMB or JAM messagebase. What this switch does is very simple to
explain. As you can see in the command syntax, after the "-L" switch
you must specify the name of a file. This file must be in a plain-
vanilla-ASCII format and must contain the names of the areas that you
want scanned by FastEcho in Squish and *.MSG messagebases. Assuming
that the filename containing your choosen areas is SFAREA.TXT, you
ought to invoke this command as follow:
FastEcho SCAN -LSFAREA.TXT
Note that there are no spaces between the "-L" switch and the "file-
name". When you perform the "SCAN" operation in this way, FastEcho will
immediately look into the specified file (SFAREA.TXT), read the areas
names and execute all the operation relative to the "SCAN" function
over the indicated areas only.
───────────────────────────────────────────────────────────────────────
- 116 -
FastEcho MANUAL - Using FastEcho -
───────────────────────────────────────────────────────────────────────
6.4 - FastEcho Pack
-------------
FastEcho has a built-in, high performance NetMail-packer/router
that can be called by invoking FastEcho with the Pack main switch. But
what does the NetMail-packer/router really do? It will bring the
NetMail messages contained in the primary NetMail directory, archiving
them in an ARCmail bundle, having, like the ones containing EchoMails,
its ARCmail attach addressed (routed) to the system that fits your rou-
ting directives. The FastEcho router normally involves any NetMail
message without priority attributes (Crash, Direct, Immediate, File/At-
tach, File/Request and so on. See in appendix C for a complete at-
tributeslist) but, if the netmail having the aforesaid high priority
attributes has the InTransit (non-local)flag too, then it will be
packed anyway. When "FastEcho Pack" is invoked without special routing
statements, by default, it automatically takes, from your configuration
setup, the default routing that you specified in "Node Manager" (see:
5.5.1.24.2 - F2-Routing), otherwise it will strictly follow your more
detailed routing statements that you may directly specify on the
"FastEcho pack" command line or, moreover, specifyed inside the
special route file (ROUTE.FE). There will be more details in the fol-
lowing chapters.
6.4.1 - Routing (commandline) Statements
This is the first advanced methods, to perform the NetMail packing
routing, provided by FastEcho (I remind you that the standard method is
the normal "FastEcho pack" without any additional parameter). The syn-
tax of this first advanced method is the following:
FastEcho PACK <addr> <addr> <...> via <ADDR>
As you can see, this syntax is subdivided in two main parts: The
standard "FastEcho PACK" commands followed by a set of addresses (cal-
led "involved NetMail addresses" set) and a single address that follows
the "Via" statement (called "target address"). The purpose of this syn-
tax is to allow FastEcho to gather, in one single ARCmail bundle, all
the unsent NetMail messages located in the "Primary NetMail Area"
which are addressed to any of the systems specified in the "involved
NetMail addresses" and preparing them to be sent to the system speci-
fied in the "target address".
6.4.1.1 - ShortCuts (wilcards/abbreviations)
In order to obtain an improved flexibility using the "PACK" com-
mand, FastEcho provides the use of some abbreviated statements, wild-
carded addressing, and macros.
6.4.1.1.1 - Shortened points routing
To enable FastEcho routes to quicker the NetMail for all your
points, it provides the choice to use a shorter route syntax:
FastEcho Pack <point number> <point number> <....>
───────────────────────────────────────────────────────────────────────
- 117 -
FastEcho MANUAL - Using FastEcho -
───────────────────────────────────────────────────────────────────────
For example, if your system has five points you can quickly route
and pack the NetMail for them by formulating the command as follow:
FastEcho pack .1 .2 .3 .4 .5
as you can see, it is short and effective.
6.4.1.1.2 - Wildcarded addressing
The addresses specified in the "FastEcho PACK" command supports the
so called, wildcarded addressing. The "wilcards" are very useful to in-
volve groups of addresses, having a common key, with a single defini-
tion. You certainly already know the use of DOS wildcard; well, their
use, in this case, is exactly the same but, instead of acting upon fi-
les, here, they will be used with NetMail addresses. For example, in-
volving, with a single definition, all the fidonet systems belonging to
"Zone 2", you should simply specify: " 2:* ". Another possibility is
using the '?' wildcard, for example "2:2448/4??". Let's see some
examples:
6.4.1.1.3 - Direct Routing Examples
1) - If You want to route all the NetMail messages addressed to the
region 33 through the system 2:331/500 your complete command will
be the following:
FastEcho PACK 2:33* VIA 2:331/500
2) - If you want to route all the NetMail messages addressed to the net
332 (in zone 2) via the system 2:332/300 you should define your
routing command as specified below:
FastEcho PACK 2:332/* VIA 2:332/300
3) - If you want to route all your NetMail addressed within the zone 2
(FidoNet) via the 2:332/300 node and all your NetMail addressed to
the zone 16 (ZyXELnet) via the node 16:600/400, then you should
define your routing command as follows:
FastEcho PACK 2:* VIA 2:332/300
FastEcho PACK 16:* VIA 16:600/400
4) - If you want to route all your NetMail addressed to the net 332,
333 and 335 via the node 2:331/500, you should define the routing
command as explained below:
FastEcho PACK 2:332/* 2:333/* 2:335/* VIA 2:331/500
5) - If you want to route all your NetMail addressed to the systems
2:331/500, 2:331/501, 2:331/502, 2:331/503 and all their points,
and to the zone 1 via the system 2:331/500 and, the remaining net-
mail addressed within the zone 2, 3, 4, 5 and 6 via the system
2:332/300 then, your routing command will look like the following:
FastEcho PACK 2:331/50?.* 1:* VIA 2:331/500
FastEcho PACK 2:* 3:* 4:* 5:* 6:* VIA 2:332/300
───────────────────────────────────────────────────────────────────────
- 118 -
FastEcho MANUAL - Using FastEcho -
───────────────────────────────────────────────────────────────────────
As you can see, the addresses could be easily and efficiently mana-
ged according to your needs. Keep in mind that, inside your batch file,
the routing sequence will be performed "top down" and remember that,
furthermore, FastEcho "PACK" won't touch NetMails that include a
^aFLAGS kludge in it, except those only containing PVT, K/S or CFM
(Private/Priviledged, Kill /Sent and Confirmation Receipt Request) and
some other flags.
6.4.2 - FastEcho Pack -R<route filename>
As said before, FastEcho supports another advanced method to per-
form the NetMail-packing/routing. This one is newer, more advanced and
flexible than the previous one. All you need is to create a plain ASCII
file containing some routing statements (that we shall see later in the
next paragraph) specifying it after the "-R" commandline switch. It,
pratically, must be placed where <route filename> is specified. For
Example: if your ASCII file containing the NetMail routing statements
is named "ROUTE.FE" your commands look like the following
FastEcho PACK -RROUTE.FE
When FastEcho is be executed in this way, it will read the contents
of the ROUTE.FE file performing the NetMail routing as specified by way
of the route-commands contained therein.
6.4.2.1 - Routing (file) statements
There are several commands that you can use inside the routing fi-
le, each one with its specific meaning.
Each statement must fit in a single line. Remember that, inside
the ROUTE file, the statements will be processed with top-down
hierarchy, which means that the LAST statement which matches the
destination address of a NetMail message to be processed is used for
routing the message. All the NetMail addresses that you will use
inside the route-file supports the wildcarded addressing (as we have
seen in the chapter 6.4.1.1.2). Furthermore, remember that NetMails can
only be routed via or to systems already defined in the Node-
Configuration. That's all. Let's now see each of them in detail.
6.4.2.1.1 - ROUTE-TO <addr> <addr> [<addr> <...>]
┌──┴───┐├────────────────────┤
│target││ involved addresses │
This routing command implies that you want FastEcho to route, via
the address specified in <target system>, all the still unsent NetMail
messages matching the addresses specified in "<addr> [<addr>]" that
FastEcho will be able to find in the "Primary NetMail Area". For exam-
ple, if you want to route all the NetMails for zone 2 via the system
2:331/501 your routing command will look like the following:
ROUTE-TO 2:331/501 2:*
───────────────────────────────────────────────────────────────────────
- 119 -
FastEcho MANUAL - Using FastEcho -
───────────────────────────────────────────────────────────────────────
while, if you want to route all the NetMail messages addressed
within the zone 2, 3, 4 via the 2:331/501 system, and all the NetMail
messages addressed to zone 1, 5, 6 via the 2:332/300 system, your rou-
ting statements will look like the following:
ROUTE-TO 2:331/501 2:* 3:* 4:*
ROUTE-TO 2:332/300 1:* 5:* 6:*
6.4.2.1.2 - NO-ROUTE <addr> [<addr> ...]
This represents a ROUTE exception. When the "NO-ROUTE" statement is
used, then all the NetMails addressed to any systems specified in the
address-list "<addr> [<addr>]", and all their points, won't be routed
but will be packed directly to these systems without routing. For exam-
ple, if you want to route all NetMails for region 33 via system 2:332/1
except the ones addressed to systems 2:332/303, 2:333/310 and all their
points, which, instead, must be packed and sent separately, you can use
the following statements:
ROUTE-TO 2:332/1 2:33?/*
NO-ROUTE 2:332/303 2:333/310
6.4.2.1.3 - DIRECT <addr> [<addr> ...]
The "DIRECT" works exactly as the "NO-ROUTE" statement with the
only difference that while the "NO-ROUTE" statement packs also the Net-
Mails addressed to a point system via its boss node (if the boss node
is specified in <addr>), the DIRECT, instead, doesn't, forcing the
NetMail addressed to be packed separately and DIRECTLY for that point.
6.4.2.1.4 - EXCEPT <addr> [<addr> ...]
This routing command, when used, will cause an "exception" that ap-
plies to the previous statements only. This will result very useful in
case of multiple uplinks/downlinks in the same network. For Example, if
you want to route all the NetMails addressed to zone 2 via the
2:331/500 system except the NetMails addressed to net 332 that you want
route via the 2:332/300 system and, within this last, except the
NetMails addressed to the 2:332/317 and 2:332/314 that you want routed
via the 2:332/315 system you must plan your route file as follows:
ROUTE-TO 2:331/500 2:*
EXCEPT 2:332/*.*
ROUTE-TO 2:332/300 2:332/*.*
EXCEPT 2:332/317.* 2:332/314.*
ROUTE-TO 2:332/315 2:332/317 2:332/314
6.4.2.1.5 - FORWARD-TO <addr>
The FORWARD-TO routing command, only involves netmail messages ha-
ving the in-transit flag set. This command is intended to right iden-
tify the system (or systems) qualified to receive all the in-transit
netmails forwarded and routed by your system. By using this command,
only the in-transit messages addressed to the systems pointed out in
<addr> will be packed and routed, otherwise FastEcho-pack won't touch
any. For example:
───────────────────────────────────────────────────────────────────────
- 120 -
FastEcho MANUAL - Using FastEcho -
───────────────────────────────────────────────────────────────────────
FORWARD-TO 2:332/300
lets FastEcho-pack to route all in-transit messages for 2:332/300;
FORWARD-TO 2:332/*
lets FastEcho-pack to route the in-transit messages addressed to
system in the net 332;
FORWARD-TO *
lets FastEcho-pack to route all the in-transit message. Use this
one if you don't need the selective FORWARD-TO feature.
6.4.2.1.6 - FORWARD-FOR <addr>
The FORWARD-FOR command also is intended for treatment of in-
transit netmail message. In this case the command allows the routing of
in-transit netmail messages having as sender a qualified address only.
In other words, this mean that can be routed only the in-transit
messages sent by sender having the address pointed out in <addr>. For
Example:
FORWARD-FOR 2:332/300
lets FastEcho-pack to route the in-transit messages sent to you by
the system 2:332/300;
FORWARD-FOR 2:332/*
lets FastEcho-pack to route the in-transit messages sent to you by
the systems becoming to net 332;
FORWARD-FOR *
lets FastEcho-pack to route all the in-transit message without
regards. Use this one if you don't need the selective FORWARD-FOR
feature.
6.4.2.2 - routing address' macro
In order to facilitate the user to setup his route-file, FastEcho
provides a complete macro-set that can be used freely inside your ad-
dresses specification.
6.4.2.2.1 - MYZONE
When used in a routing statement, FastEcho will automatically ex-
pand it with your zone address (zone:*). Note that the zone will be the
zone of your primary network address. For example, To route all NetMail
addressed to your zone via the system 2:393/393 you can use the follo-
wing command:
ROUTE-TO 2:393/393 MYZONE
───────────────────────────────────────────────────────────────────────
- 121 -
FastEcho MANUAL - Using FastEcho -
───────────────────────────────────────────────────────────────────────
6.4.2.2.2 - MYNET
This convenience macro will be expanded to all systems in your NET
when specified within a routing line (zone:net/*), like the previous
macro, this net will be the same as your primary network address. For
example, if you want to route all the NetMails addressed within your
net, through system 2:332/301 you might use the following command:
ROUTE-TO 2:332/301 MYNET
6.4.2.2.3 - MYPOINTS
This macro will be automatically expanded to <zone>:<net>/<node>.*,
in order to route to your points the NetMail messages addressed to
them, that FastEcho will be able to find in the "Primary NetMail Area".
While the other macros will expand only for your MAIN address, this
one, instead, will be conveniently expanded for *ALL* your network
addresses (your main address and all your akas); thus it will be very
useful if you are involved in more that one network and you feed point
under each one of them. If you want perform the routing operation for
all your points, processing their NetMail messages by means of one sin-
gle routing command, then, simply use the following:
DIRECT MYPOINTS
2.4.2.2.4 - LISTED
The LISTED macro will be expanded in the addresses of all systems
configured in your node manager. It may be useful if used in combina-
tion with the NO-ROUTE and the DIRECT macros. If you want, for example,
pack NetMails for all your downlinks and their points, uplinks and
their points, and, finally, your points separately, you could use the
following command:
NO-ROUTE LISTED
DIRECT MYPOINTS
Furthermore, if you wish for the NetMails addressed to all sys-
tems defined in FESetup's Node-Configuration to be packed directly
without routing them, including the points of each node listed unless
the points are listed in your node manager, you can use the following
command:
DIRECT LISTED
6.4.2.3 - ROUTE.FE examples
Let's now see some pratical examples. Keep in mind that what you
will see in this paragraph are all statements that must be contained in
a file: the one you will specify in the FastEcho PACK -R<file> command.
───────────────────────────────────────────────────────────────────────
- 122 -
FastEcho MANUAL - Using FastEcho -
───────────────────────────────────────────────────────────────────────
Hypotesis 1)- Your system (2:331/999) has an Uplink (2:331/500) for Fi-
doNet, three downlinks (2:331/331, 2:331/332, 2:331/333),
and 4 points 2:331/999.1, .2, .3, .4. You want to route
all your outgoing NetMail (from you and from your down-
links) via your Uplink (2:331/500), then, as normal, you
want to route all your incoming NetMail to your downlinks
(points included). Your route file will look like the
following:
ROUTE-TO 2:331/500 MYZONE
NO-ROUTE 2:331/331 2:331/332 2:331/333
DIRECT MYPOINTS
Hypotesis 2)- Your system (2:331/940) has two akas (16:700/631 and
39:230/431). Three uplinks: one for fidonet (2:331/900),
one for ZyXELnet (16:700/600) and the last for AmigaNet
(39:230/400). You, furthermore, have 3 downlinks and 3
points for ZyXELnet (16:700/711, 16:700/712, 16:700/713)
and (16:700/631.1, 16:700/631.2 and 16:700/631.3); one
downlink and two points for FidoNet: (2:331/941) and
(2:331/940.1, 2:331/940.2) and, last of all, three down-
links and 2 points for AmingaNet (39:230/432, 39:230/433,
39:230/434) and (39:230/431.1, .2). In particular you
must route all NetMail for (2:331/942 and 2:331/943 via
the 2:331/941 downlink) Your route file will look like
the following:
ROUTE-TO 2:331/941 2:331/942 2:331/943
NO-ROUTE 16:700/711 16:700/712 16:700/713
ROUTE-TO 39:230/432 39:230/433 39:230/434
ROUTE-TO 2:331/900 1:* 2:* 3:* 4:* 5:* 6:*
ROUTE-TO 16:700/600 16:*
ROUTE-TO 39:230/400 39:*
DIRECT LISTED
6.4.3 - FastEcho Pack -I
When FastEcho Pack is issued with the "-I" commandline switch,
FastEcho will involve in the packing oparations only the NetMails ha-
ving the attrubute "In-Transit" set. The "-I" switch could be used
either in CommandLine Routing (see chapter 6.4.1) and in File Routing
(see: chapter 6.4.2).
6.4.4 - FastEcho Pack -F
As we have seen at the beginning of the chapter 6.4, normally, the
FastEcho NetMail packer-router creates, in the OUTBOUND directory, the
ARCmail bundles containing all the NetMail to be routed, with an ARC-
mail attach in the "Primary NetMail Area", addressed to the target sys-
tem which these ARCmail bundles must be sent to; but if you specify the
"-F" switch in your "FastEcho Pack" command, this ARCmail attach won't
be created at all. This switch must be used only in particular situa-
tions, for example when working in LAN environments. Don't specify this
switch unless you are perfectly aware of what you are doing.
───────────────────────────────────────────────────────────────────────
- 123 -
FastEcho MANUAL - Using FastEcho -
───────────────────────────────────────────────────────────────────────
6.4.5 - FastEcho Pack -P
When the command FastEcho Pack is invoked with the "-P" switch, it
will use the Binkley style NetMail packing, including all NetMails ha-
ving priority flags such as direct, crash, F/att, F/req in the pack
operation;the IMM flag is supported only working in PoP and McMail en-
vironments creating the correct *.IUT files. In addition all NetMails
addressed to unknown points will be routed to their boss node unless
the DIRECT flag is specified. Note that, if the NetMail messages are
originated by one of the system's AKAs but don't have the LOCAL flag,
they won't be packed at all.
6.5 - FastEcho Afix
-------------
This command enables FastEcho to start the processing of valid
AreaFix requests which it will be able to find in the "Primary NetMail
Area". We have extensively explained what an AreaFix request is, in the
chapter 5.5.5 where we pointed out all the AreaFix MetaCommands too
(see: chapter 5.5.5.1); furthermore we dealt with AreaFix several times
throughout this manual: (see: 5.4.5.2, 5.5.1.5.2, 5.5.1.6.2, 5.5.1.8,
5.5.1.9, 5.5.1.18, 5.5.1.19, 5.5.1.20, 5.5.1.21, 5.5.3.1.10, 5.5.3.1.14
5.5.3.1.19, 5.5.3.1.20 and, finally, in all the chapter 5.5.6) so i'm
somewhat sure that you already know the subject we are now talking
about but, all the same, I wish to remind you that an AreaFix request
is, mostly, the way in which your downlinks join or unlink their Echo-
Mail available areas themselves, automatically and without any of your
manual intervention. They simply have to send your system an "AreaFix"
request, which is nothing more than a normal NetMail message addressed
to the "AreaFix" processor of your system and contains in its body one
or more "MetaCommands", and waits until your "Built-In" FastEcho Area-
Fix processor works for them. Furthermore, as already mentioned in the-
se chapters, I want remind you that all the AreaFix MetaCommand will be
processed with top-down hierarchy; this puntuaction may be useful when
you try to compose your first AreaFix requests. In any case refer to
the examples reported in this manual in the chapter 5.5.5 and refer to
the same chapter whenever you are in doubt about any of the AreaFix
options.
6.6 FastEcho Notify
---------------
By using this command you can manually force FastEcho to generate a
NetMail message containing a lot of information about the agreement ma-
de between you and your downlinks. The notify message is the same that
will be sent automatically from AreaFix when it receives the %INFO me-
tacommand (see chapter 5.5.5.1.6). In this way, you can choose the sys-
tem which the Notify message will be sent to; this can be done by spe-
cifying, after the "FastEcho NOTIFY" command, the address or the ad-
dresses of the system (or the systems) that you prefer. The address
wildcarding is also allowed. If you run this command without any para-
meters, FastEcho will send the Notify message to any system having the
"Send Notify" option toggled to "Y" (see 5.5.1.20). Here are some exam-
ples to send the Notify Messages:
───────────────────────────────────────────────────────────────────────
- 124 -
FastEcho MANUAL - Using FastEcho -
───────────────────────────────────────────────────────────────────────
If you want send the Notify message to your points, assuming your
system has four points, you should use the following command:
FastEcho NOTIFY .1 .2 .3 .4
If your main address is 2:787/43 and you want to send the notify
message to your downlink 2:787/45 (which is the node 45 in the network
of your main address) you can use the following command:
FastEcho NOTIFY 45 (or) FastEcho NOTIFY 787/45
If you wish to send the notify message to all system configured in
your node manager belonging to zone 2, then you can use the following
command:
FastEcho NOTIFY 2:*
If you, instead, wish to notify one or more systems in particular,
you may specify their complete address:
FastEcho NOTIFY 2:332/300 2:331/501
Will send the notify messages only to the systems specified. Remem-
ber that you cannot, of course, send a notify message to a system not
previously configured in "Node-Manager".
6.6 - FastEcho Help
When FastEcho is locally invoked with the "HELP" switch, it will
generate a NetMail containing a help message about the use of AreaFix,
addressed to the system specified after the "HELP" switch. If "FastEcho
HELP" is invoked without additional addresses then, the help message
will be sent to all systems having the "Send Help" option toggled to
"Y" in node manager (see 5.5.1.21). The message you wish to be sent is
fully configurable by you. In fact you can build a file in your prefer-
red language, more, or less detailed according to your preferences. In
this way you can easily send this file manually. It may be useful when
you join a new downlinks in order to directly inform it about the capa-
bilities of your AreaFix. The default AreaFix Help File enclosed in the
FastEcho distribution archive is named AreaFix.HLP. You can specify a
different one by means of the option we have already seen in the para-
graph 5.5.6.12. The Format is the following:
FastEcho HELP <Address> <Address> <...>
If you want, for example, to send a help message for AreaFix usage
to system 2:116/324 simply input the following command:
FastEcho HELP 2:116/324
For this command, all the conveniences provided by wildcard or mul-
tiple addressing still remains valid.The same help-file could also be
requested by your downlinks through an AreaFix request containing in
its body the command %HELP (we have seen in the chapter 5.5.5.1.20).
───────────────────────────────────────────────────────────────────────
- 125 -
FastEcho MANUAL - Using FastEcho -
───────────────────────────────────────────────────────────────────────
6.7 - FastEcho Relink
This command may conveniently be used to link (or relink) all your
active areas upon an uplink after you've unlinked them. The relink
operation is done by mean of an AreaFix request generated automatically
by FastEcho the FastEcho Relink command is issued.. The relink command
may be used in a general-mode: when issued without any trailing
address, or in a specific-mode: when, instead, almost one address is
specified. When the Relink command is started without addresses
(general mode) the AreaFix message will be sent to all system you
settled in the Forward Areafix request manager (see chapter 5.5.6.15).
If, instead, one or more trailing address are present, then FastEcho
creates the netmail messages for the specified systems only. Note that
in the automatic request message FastEcho uses the AreaFix notation
you settled for each system in Node Manager -> AreaFix flags. (See
paragraphs 5.5.1.18 through 5.5.1.18.11)
6.8 - FastEcho Stat
It may be useful for you, to have the choice to generate statistics
about the percentages of mail sent/received between you and your down-
links and/or sent/received between you and your uplinks. This can be
done by means of the built-in FastEcho statistical function. In order
to keep your daily statistics, FastEcho keeps one specific database up-
dated (named FastEcho.DAT) every time a SCAN or TOSS operation will be
performed on your system. When this command is invoked from the DOS
prompt it will generate an ascii file (Human readable) containing all
the statistics of your system. The name of the statistic file can be
fixed by you in FESetup (look at chapter 5.4.5 for details). With this
utility it will be possible to generate group-statistics too, simply by
specifying them. Let's see the switches which make these operations
possible.
6.8.1 - FastEcho Stat -R
Normally, when FastEcho Stat is invoked, it creates the statistic
file basing itself upon the contents of the aforesaid statistic data-
base (FastEcho.dat) generating an overall statistic report. It may hap-
pen that you need to generate new statistics monthly, weekly or daily;
in this case you must, everytime, specify the "-R" switch in order to
allow FastEcho automatically zeroise the FastEcho.DAT file when it fi-
nishes generating the statistics you ordered; in this way, the next ti-
me that FastEcho stat is invoked, it will only show the statistics re-
lative to the EchoMail traffic after the last "STAT -R" command.
6.8.2 - FastEcho Stat -RS
This command performs the same operation as the previous one "-R"
but, moreover, it will also reset also the data records of the amount
of messages sent/received to/from each system configured in "Node
Manager".
6.8.3 - FastEcho Stat -S
When FastEcho Stat is invoked with the Switch -S then FastEcho
omits the system statistic from the final report. In this case only the
area statistics will be shown.
───────────────────────────────────────────────────────────────────────
- 126 -
FastEcho MANUAL - Using FastEcho -
───────────────────────────────────────────────────────────────────────
6.8.4 - FastEcho Stat -G<groups>
When the "-G" switch is specified after the "FastEcho Stat" com-
mand, specifical statistics belonging to the groups (one or more) spe-
cified after the "-G" switch is generated. In the generated report
there will also be included all the systems that have access to one or
more of the specified groups. If, for example, you want to generate the
statistics for the areas belonging to the groups A,B,C,D and for all
the systems that have access to one or more areas of the same too, then
your command will look like the following:
FastEcho STAT -GABCD
6.8.5 - FastEcho Stat -H
By default the statistic generationwon't include the areas marked
as Hidden (see: Hide Area at the chapter 5.5.3.1.20). If this switch is
used when invoking the "FastEcho Stat" command, you will force
"FastEcho Stat" to include, in its report, all areas, although pre-
viously marked as "hidden".
6.8.6 - FastEcho Stat -N
Normally, FastEcho won't include, in its statistical report, the
areas that have no traffic because this is somewhat useless. If you
need to list these areas too, then specify the "-N" switch after the
FastEcho Stat command. All your no-traffic areas will be included.
6.8.7 - FastEcho Stat -O
By default, when a new statistic is performed, FastEcho doesn't de-
lete the old statistic file but the new statistics will be appended to
it. If you need the old statistic file to be overwritten, however, spe-
cifying the "-O" switch to the "FastEcho Stat" command will be enough.
The use of the "-O" switch may be useful in case of automatic procedu-
res, handled by means of batch files, directed to automatically post
the monthly or weekly statistic results to downlinks, uplinks or in
EchoMail areas, (we shall see later one example in "FEUTIL Post"
command).
7 - USING FEUTIL
============
After we have seen the pratical use of the FastEcho main program
and all its switches and sub-switches we shall begin to see the Fast-
Echo companion program: FEUTIL. It really performs a lot of operations
such as: building a new index for your HMB and JAM messagebases, reply-
linking the messages contained in your HMB, JAM and *.MSG messagebases
in order to allow you follow the threads easily; starting the purging
operation basing itself upon your purging parameters set in "FESetup"
and much, much more. Most of the available FEUTIL commands, support
multiple messagebases (HMB, JAM or Fido *.MSG). Like the "FastEcho.exe"
command, FEUTIL has its help screen. If you invoke it without any para-
meters you will obtain the following primary help screen:
───────────────────────────────────────────────────────────────────────
- 127 -
FastEcho MANUAL - Using FEUtil -
───────────────────────────────────────────────────────────────────────
---------------------------------------------------------------------
Usage:
FEUTIL INDEX - [HJ-] - Create new index files
FEUTIL LINK - [HJM] - Reply-link messages and 'clean' subjects
FEUTIL PURGE - [HJM] - Delete mess. according to age and/or number
FEUTIL PACK - [HJM] - Pack messagebase and opt. renumber messages
FEUTIL SORT - [HJ-] - Sort unread mess. by board by and date
FEUTIL CHECK - [H--] - Check messagebase errors (crosslinks etc.)
FEUTIL UNDELETE - [H--] - Undelete all messages (on a special area)
FEUTIL MOVE - [H--] - Move messages from one area to another
FEUTIL POST - [HJM] - Post a textfile as message into an area
FEUTIL IMPORT - [HJM] - Import NetMails into NetMail-areas
---------------------------------------------------------------------
As you can see, every function is followed by one or more letters
enclosed in square brackets. These letters identify the function
availabilities for the indicated messagebases: "H" for HMB, "J" for JAM
and "M" for Fido *.MSG; You can easily select the messagebase you want
FEUTIL to act upon, simply by specifing the following switches:"-JAM"
for JAM, "-HMB" for HMB or "-FIDO" for Fido *.MSG messagebases. For
example, if you want FEUTIL to perform the index operation upon the JAM
messagebases only, you should simply input the following command from
the DOS prompt:
FEUTIL LINK -JAM
By default FEUTIL will act upon all your configured messagebases. If
you, further, need more detailed online help about one particular FEU-
til function,you can obtain it simply by inputting the complete command
followed by a question mark. For example, if you need more help about
the FEUTIL PURGE function you can use the command: "FEUTIL PURGE ?" (Or
FEUTIL PURGE /?) Obtaining the following informations
---------------------------------------------------------------------
FEUTIL PURGE - Delete messages according to date and/or number.
<switches>
-DELETE : Delete messages in unknown boards
---------------------------------------------------------------------
Let's now see each of the FEUTIL functions in detail.
7.1 - FEUTIL Index
------------
When you use the "FEUTIL Index" command, your Hudson and JAM mes-
sagebases will be reindexed. Performing a full indexing of your messa-
gebase may be helpful whenever you notice that your messagebase index
are corrupted or not updated. This may happen in the case of a sudden
lack of electrical energy while your system is working on messagebases
index or, further, in case of messagebase overflow. We have seen, in
the paragraph 5.5.3.1.6 that the Hudson Message Base is composed of
several files. In this case The "FEUTIL Index" program will regenerate
the following HMB index files:
───────────────────────────────────────────────────────────────────────
- 128 -
FastEcho MANUAL - Using FEUtil -
───────────────────────────────────────────────────────────────────────
MSGIDX.BBS This file contains the messagenumber and board of
each record in the messagebase
MSGTOIDX.BBS This file contains the names of the addressees of
each record in the messagebase
MSGINFO.BBS This file contains global information about your
messagebase regarding the number of messages (on
each board, highest/lowest message etc.)
For JAM areas it only recreates the .JDX file out of the info
found in the .JHR file.
7.2 - FEUTIL Link
-----------
The "FEUTIL Link" function provides an easy and immediate way of
building the so called reply-link chains within your HMB, JAM or *.MSG
messagebases. But what is the "reply chain"? When the "FEUTIL Link"
function is invoked it starts scanning your messagebases in order to
find the answers (reply) to any messages generating the proper link
between them. For example:
┌──>(1) From:Bob Jopers (4) From:Kitty Kant
│ To:Maxx Berni To:John Candy
l│ Subj:FastEcho Subj:Hi there!
i│
n│ (2) From:Reed Richards l┌───>(5) From:Bob Jopers
k│ To:Ben Grimm i│ To:Maxx Berni
│ Subj:Doc.Destiny n│ Subj:FastEcho
│ k│
└──>(3) From:Maxx Berni ───────┘ (6) From:Reed Richards
To:Bob Jopers To:Jonny Storm
Subj:FastEcho Subj:Flames
Assuming that the headers shown above are message headers within a
board in your HMB or JAM or Fido messagebase.When you start the
"FEUTIL Link" function, it will create a connection upon three messa-
ges:
(1) -> (3) -> (5)
In fact, as you can see, the message (1) is the first one, message
(3) is the first reply to the (1) and message (5) is a subsequent reply
to message (3). As many "replies" will exist in a board, as many reply-
links FEUTIL will create. Furthermore, the connections created among
messages' replies, will be useful and convenient so that you can easily
follow all the discussions (as known as "thread") existent in one or
more boards, within your messagebase, by means of your messagebase edi-
tor. "FEUTIL Link" can establish the replies-link thanks to the hidden
───────────────────────────────────────────────────────────────────────
- 129 -
FastEcho MANUAL - Using FEUtil -
───────────────────────────────────────────────────────────────────────
message kludges. Every message, in fact, has got a unique hexadecimal
number, called MSGID (^AMSGID); the messages that reply to the original
one will have their unique MSGID of course, but, furthermore, they have
another particular hidden kludge called REPLY (^AREPLY) that refers to
the ^AMSGID number of the message they have replied to; In this way the
connection can be made. In the same example seen above, the messages
linked will have the following kludges:
(1) From:Bob Jopers (3) From:Maxx Berni (5) From:Bob Jopers
To:Maxx Berni To:Bob Jopers To:Maxx Berni
Subj:FastEcho Subj:FastEcho Subj:FastEcho
--------------- --------------- ---------------
^AMSGID:15aab3c ^AMSGID:ff3a2ab ║─┐ ^AMSGID:86c002a
═══╤═══ ^AREPLY:15aab3c │ ^AREPLY:ff3a2ab
│ ═══╤═══ │ ═══╤═══
└─────────────────────┘ └──────────────┘
As you can immediately see, the MSGID kludge of the first message
matches the REPLY kludge of its first answer (3), while, the MSGID of
this first answer matches the REPLY kludge of the second answer (5),
which is, pratically, the reply to the reply.... and so on.
7.2.1 - FEUTIL Link -F[orce]
In order to speed up the link operation, FEUTIL, normally, uses a
particular file called "IMPORT.XYZ" (.JAM, .SDM for the other message
base types)created by "FastEcho Toss". This file, internally, has
stored a list of areas in which new messages are present since the last
toss. In this way, FEUTIL avoids rescaning all your boards in all thee
messagebases by directly aiming to the ones reported in this file.
Nevertheless, FEUTIL can work without this support file too, but, if
the present switch is specified, FEUTIL will be forced to use it. When
this switch is used and no IMPORT.??? file is not found, no further
actions will be taken.
7.2.2 - FEUTIL Link -I[gnore]
As opposed to the previous one, the "-I" switch will force FEUTIL
to completely ignore the aforesaid "IMPORT.???"files, even if present.
This will result in a complete messagebase board scanning for reply
links connection. It may be useful to specify this switch in case you
already have one or more messagebases filled with messages and, up to
now, you have never linked.
7.3 - FEUTIL Purge
The "FEUTIL Purge" command starts the effective purging operation
all over your messagebases. With this function, FEUTIL starts scanning
all areas configured, marking for deletion all the messages that match
the purge specifications you set up in the "Purge Default" section of
FESetup - FEUTIL parameters (see chapter 5.4.9.1 and in the area-purge
definition of FESetup - Area Configuration (see chapter 5.5.3.1.22) As
we have seen in these chapters, the purge operation doesn't physically
remove the messages; it only marks them for deletion and "FEUTIL PACK"
command does the rest (as we shall see in the next paragraph). The
"FEUTIL Purge" is normally executed if your HMB messagebase reaches its
limits (about 16.000 messages), but it can be performed whenever you
───────────────────────────────────────────────────────────────────────
- 130 -
FastEcho MANUAL - Using FEUtil -
───────────────────────────────────────────────────────────────────────
want, according to your needs. (I.E. the JAM and the Fido messagebases
don't suffer from this limitation and the maximum number of messages
held by them is limited only by the operative systems internal limits,
but, an excessive number of messages in your messagebases may impugn
your system performances). FastEcho provides an easy way of letting
your batch-file detect when the Hudson Message Base is going to excede
its limits: by means of the Flag-File PACKHMB.FE. FastEcho, in fact, it
creates this file in its system directory, during the "TOSS" operation,
when it senses that the messages should be tossed beyond the HMB
limits. If FastEcho notices the HMB limits approaching, then it creates
this flag-file and stops any further toss or import operation to avoid
the messagebase overflow.
7.3.1 - FEUTIL Purge -D[elete]
The "-Delete" switch, appended to your "FEUTIL Purge" command, will
cause, after the normal purging (we have seen in the previous para-
graph), the complete deletion of all messages belonging to undefined
boards. It may happen, in fact, that in your current configuration, you
decide to delete one or more EchoMail, NetMail or Local boards, by
using the "Del" function seen in chapter 5.5.3.1.26.7 of FESetup. At
this time, the messages already exsistent in your messagebase, still
exist but their board is undefined (because it has been just deleted to
you). If these undefined messages have really become useless for you,
you may decide to definitely remove them in order to free more disk
space. This is the time to use the "FEUTIL Purge -Delete" command.
7.4 - FEUTIL Pack
-----------
The "Pack" is the operation that PHYSICALLY REMOVES all the messa-
ges that, in your messagebase, have been marked as deleted by the
"Purge" operation (or manually by your editor) we have seen in the
previous paragraph. When "FEUTIL Pack" is invoked without any
additional parameters, it performs the packing operations in the
maximum security by keeping the old messagebase while it creates a new
clean one. The old messagebase will be removed only after the new one
has been created without errors. This method more secure than other but
it has some disadvantages: It's very "time-consuming" and, furthermore,
requires a lot of disk space to complete the operation. However, the
"Pack" function can rely upon four commandline switches and, by using
them, you can fine tune its performances. Let's see them in detail.
7.4.1 - FEUTIL Pack -F[orce]
The use of the "-F" switch may be helpful if you are short on disk
space. As we have seen in the previous paragraph, normally, the "Pack"
function needs a lot of free disk space to correctly perform its opera-
tions, about twice of the space of your current messagebase. That's
because, normally, for security purposes, your current messagebase is
left untouched until FEUTIL finishes all the operations upon the new
"packed" messagebase. By using the "-F" switch, instead, FEUTIL will
always overwrite the old unpacked messagebase while it creates the new
"packed" one. This method has two advantages:It doesn't need free disk
space and the new "packed" messagebase, which it creates, is less frag-
mented than the one created without overwriting; and one disadvantage:
you can totally lose your messagebase data if the "Pack" operation is
───────────────────────────────────────────────────────────────────────
- 131 -
FastEcho MANUAL - Using FEUtil -
───────────────────────────────────────────────────────────────────────
interrupted during its execution. This switch only has effect upon the
Hudson Message Base.
7.4.2 - FEUTIL Pack -O[verwrite]
Using the "-O" switch, you will obtain, approximately, the same
results seen before in paragraph 7.4.1 and 7.4, but, in this case, you
allow FEUTIL to senses if, on your hard disk drive, exists enough free
space to correctly perform the "maximum security" packing (7.4),
otherwise FEUTIL automatically switches to the method seen in the
paragraph 7.4.1. Pratically, the "-Overwrite" switch will cause FEUTIL
to only overwrite the messagebase if short on disk-space. If you use
this switch or not depends on you only. Without this switch FEUTIL will
quit its operation without packing your messagebase if short on disk-
space. It only has effect upon the Hudson Message Base in this case
too.
7.4.3 - FEUTIL Pack -R[enumber]
When this switch is used, FEUTIL will perform its packing operation
and furthermore it will force the renumbering of the whole messagebase,
updating the lastread pointers too (the lastread pointers are flags
that point to the last message you read in any board of your message-
base). I wish to remind you that FEUTIL has an "automatic renumber" de-
vice that automatically intervenes, without specifing the "-R" switch
too, during the normal "Pack" operation, whenever it detects that the
highest messagenumber in your HMB is higher than the limits you defined
in FESetup for "Autorenumber" option (see: 5.4.9.3 chapter).
7.4.4 - FEUTIL Pack -D[elete]
It may happen that your messagebase has crosslinked records. This
could be mostly due to HMB messagebase overflow, lack in electrical
energy, messagebase editor faults or other umpredictable reasons. These
are messages untidily interwoven in the MSGTXT.BBS file, and, normally,
they are unrecoverable, thus, your only solution is to delete them.
This operation can be conveniently performed by using the "-D" command-
line switch while invoking the "FEUTIL Pack" command.
7.4.5 - FEUTIL Pack -Q[uick]
This switch works only over JAM areas. It now allows improved
processing speed while packing this type of messagebase. By using the
Q[uick] switch, FEUTIL performs the "Pack" operation only over the JAM
areas where deleted messages exists, avoiding to waste precious time
trying to pack untouched JAM areas.
7.5 - FEUTIL Sort
-----------
This switch may be useful if you recognize that your messagebase
needs to be sorted by board, date and time respectively. Having your
messages sorted will help you and your user to keep the correct thread
path within your EchoMail/NetMail and Local areas reading the messages
contained in there. (For further information about the "thread" meaning
see the chapter 7.2). The "Sort" switch, when sorting, to speed up this
function, doesn't involve the whole messagebase but only the new
───────────────────────────────────────────────────────────────────────
- 132 -
FastEcho MANUAL - Using FEUtil -
───────────────────────────────────────────────────────────────────────
messages received in the last "TOSS" operation. In order to find where
the new messages begin it bases itself upon the lastread pointer
position (the lastread pointers, as said before, are flags that point
to the last message you read in any area of your messagebase). If you
need to perform a global sorting, I can only suggest you move manually
your lastread pointer upon the first message in any board within your
messagebase, by means of your preferred messagebase editor, or, better
relying upon customized messagebase tools that do the same operation
automatically, just before starting with the "FEUTIL Sort" operation.
7.5.1 - FEUTIL Sort -B[ackup]
When the "FEUTIL Sort" command is invoked with the "-Backup"
switch, before starting with the sorting operation, as explained in the
previous chapter, it creates, as precaution, a backup copy of the
MSGHDR.BBS file. The last steps remain the same as we have seen in the
paragraph 7.5.
7.6 - FEUTIL Check
------------
The "FEUTIL Check" completely analyzes your Hudson messagebase in
one pass. Might be very good practice to execute the "FEUTIL Check"
sometime upon your Hudson messagebase in order to keep it always
perfectly functional. With the "Check" operation you can discover and,
optionally, fix errors due to bad or crosslinked messages within it.
When the "FEUTIL Check" is invoked without any additional parameters it
simply feeds you back if and what kind of problems exist. If no errors
are detected, then it returns a "No errors" message. In your batch file
you can handle the results of "checking" simply by detecting the
Errorlevel 111 provided directly by "FEUTIL Check".
7.6.1 - FEUTIL Check -D[elete]
If the "FEUTIL Check" program is executed with its optional com-
mandline switch "-D" then, if it detects errors within your messageba-
se, it will try to recover them by deleting bad or crosslinked messages
and rebuilding the HMB index files: (MSGIDX.BBS, MSGTOIDX.BBS and
MSGINFO.BBS). In most cases it would be enough. It is advised that you
do not use the -Delete switch if you run CHECK from a batch file, only
use the -Delete switch if you know that and which errors are in your
HMB.
7.7 - FEUTIL Undelete
---------------
As mentioned several times, up until now, throughout this manual,
when one or more messages are marked for deletion (by means of the
"FEUTIL Purge" operation or by means of your messagebase editor), they
won't really be removed from your messagebase. Until they are
materially removed through the appropriate function (that's FEUTIL
Pack), they could always be "Undeleted". In fact, by using the "FEUTIL
Undelete" function it will be possible to restore messages that have
been previously marked for deletion. It can act both, upon selected
boards only or upon the whole messagebase (only HMB). If you wish to
restore the previously deleted messages which are present in one
particular board, then, you can specify this board after the "FEUTIL
───────────────────────────────────────────────────────────────────────
- 133 -
FastEcho MANUAL - Using FEUtil -
───────────────────────────────────────────────────────────────────────
Undelete" command. For Example, if you want to undelete all the
messages marked for deletion existing in the CHATTER.332 EchoMail board
then the command you must input from your DOS prompt will look like the
following:
FEUTIL UNDELETE CHATTER.332
If you wish, you may specify the HMB board number instead of its
EchoTag, preceding the board number by the "#" sign. So, Assuming that
the EchoMail board CHATTER.332 is the board n.29, then, in order to
perform the same operation seen above on the same board, your command
will look like the following:
FEUTIL UNDELETE #29
while, if it is used without any other additional parameter it will
scan the whole messagebase in order to search and restore any deleted
message it will be capable of discovering inside. Bare in mind that,
the "FEUTIL Undelete" command works only upon the HMB messagebase and,
furthermore, I wish to remind you that FEUTIL can't undelete any messa-
ge after the messagebase has been packed by means of the FEUTIL pack
utilities: that's because it materially removes all messages previously
marked for deletion.
7.8 - FEUTIL Move
-----------
Sometimes you may need this feature in order to pour off all messa-
ges from one board to another. It may happen, in fact, that an EchoMail
areas changes its EchoTag because it has been split into two or more
detailed EchoMail areas (For example the COMMS.ITA may be splitted and
distributed into two areas COMMS_MODEM.ITA and COMMS_PHONE.ITA). If you
don't want to miss the still present messages contained in COMMS.ITA,
then by means of your "Move" function it will be possible to preserve
them. It will be sufficient to pour off all the messages contained in
the old and, by now, useless COMMS.ITA to one of the new active boards.
For this command, like the previous, the target board may either be the
area-name or the Hudson board number preceded by the "#" sign. If you
want, for example, to move all the messages contained in the COMMS.ITA
EchoMail board into the new COMMS_MODEM.ITA board, then your command
will look like the following:
FEUTIL MOVE COMMS.ITA COMMS_MODEM.ITA
Where the COMMS.ITA represents the source board where the messages
will be picked up,and the COMMS_MODEM.ITA the target, where the messa-
ges will be moved to.
7.9 - FEUTIL Post
-----------
This powerful feature provides a convenient way to post a text file
in any your configured area: EchoMail/Local and NetMail. It may be use-
ful in several occasions, for example to insert documents manually in-
side your areas or to periodically post files or statistics by means
of batch files called automatically from your mailer's external events.
The Command's syntax is the following:
───────────────────────────────────────────────────────────────────────
- 134 -
FastEcho MANUAL - Using FEUtil -
───────────────────────────────────────────────────────────────────────
FEUTIL POST <file> <board> [-DELETE] [-From name] [-To name]
[-Subj text] [-Flags <flags>] [-Addr <address>]
It may seem complex but it isn't.
7.9.1 - <file> (mandatory)
Here you must specify the file name you wish to be posted. It has
to be a plain ascii file of course, DOS wildcards may be used to post
multiple files in one run.
7.9.2 - <board> (mandatory)
In this position you must specify the board number or the area
name in which you want your file to be posted to. You may specify the
board with two different notations: By board name, specifing directly
the area tag, or by board number. When using the HMB board number you
must always specify it preceded by the "#" sign (I.E. #1 or #154).
7.9.3 - [-Delete]
If you specify the "-Delete" switch in your "Post" command, then,
the file to be sent (defined in the paragraph 7.9.1) will be deleted
after the post operation is correctly performed.
7.9.4 - [-From name]
Here you may specify the optional sender name (I.E. -From SysOp).
Remember that, if the sender name is composed of two or more words
separated by space, then it must be enclosed within double quotes:
-From "Reed Richards"
If you don't specify any "-From" option then your message sender
will result the first user name that FEUTIL detects in your FESetup
"User Name" definition.
7.9.5 - [-To name]
In this option you may specify the addressee of the message you are
going to send. Here also, if the addressee name is composed of two or
more words separated by space, it must be specifically enclosed in dou-
ble quotes; for example, to specify Ben Grimm as addressee you must
type:
-To "Ben Grimm"
If you don't specify any "-To" option, then your message will be
automatically addressed to "All"
───────────────────────────────────────────────────────────────────────
- 135 -
FastEcho MANUAL - Using FEUtil -
───────────────────────────────────────────────────────────────────────
7.9.6 - [-Subj text]
After the optional "-Subj" option you may specify the subject of
your message. As usual, if your message subject is composed of multiple
words, then it must be enclosed within double quotes; for example,
to specify, as message subject 'this is a test' you must type:
-Subj "this is a test"
If in your "FEUTIL Post" command you don't include this option at
all, then the messages Subject will be defaulted to the name of the
posted file (see:7.9.1)
7.9.7 - [-Flags <flags>]
When posting a message by using the "FEUTIL Post" feature, you can
also decide what kind of flag (attribute) must be set in its header.
The "Post" function provides a complete set of message attributes that
you may use separately or jointly by chaining them. The available at-
tributes are the following:: Pvt, Crash, File, Freq, Kill, Hold, Dir,
Imm, Del, Trunc, CFM and RRQ. Assigning multiple flags to a single mes-
sage will be possible by joining them to the '+' chaining sign without
enclosing them between quotes; for example:
-Flags PVT+CRASH+IMM
For further details about attributes see in appendix C.
7.9.8 - [-Addr <address>]
This last option will be helpful only if you plan to use the
"FEUTIL post" function to post messages in NetMail areas, where the ad-
dressee NetMail address of the posted message will be mandatory, of
course. The NetMail address must be specified in its standard notation
after the "-Addr" option. To post a NetMail message to the 2:393/393
system you must specify the -Addr option as follows:
-Addr 2:393/393
without enclosing it between quotes. The "-Addr" option will be manda-
tory only if you have specified a NetMail board in the <board> item
(See paragraph 7.9.2). If you post a message in a NetMail board without
specifying a NetMail address in the present "-Addr" item, then no fur-
ther action will be performed.
7.9.9 - FEUTIL Post Examples & Application
As said before, the "Post" function of FEUTIL may be very useful to
let your system to automatically send periodical messages generated by
system tools such as EchoMail statistics generator (Such as FastEcho
Stat) or moreover by specifical statistic programs used normally by mo-
derators in order to post to their areas the monthly statistics about
the best or worst message writer, the best or worst message quoters and
so on. Furthermore, by means of the FEUTIL Post function you can send,
to any of your configured areas, pieces of logs and/or text messages
whenever you want. Now, in order to show an application example, we
will pretend to need to post in the SysOp.332 EchoMail area the
───────────────────────────────────────────────────────────────────────
- 136 -
FastEcho MANUAL - Using FEUtil -
───────────────────────────────────────────────────────────────────────
monthly EchoMail statistics about the areas belonging to the A,B,L,K,J
groups with, embedded, all the statistics reporting the bytes
sent/received by the systems that have access to at least one area
belonging to these groups. Furthermore, we want to post, to a NetMail
area, the statistic report of the EchoMail traffic about areas
belonging to the C,I,M,X groups and then send it to NetMail
(corresponding to the board number #2 in your Area-Definition) to the
1:323/323 "Richard Gizmo" and 1:256/767 "Bob Wisdom" systems. Then you
want to send in "File/Attach", the statistic file to "Edwin Marshall"
(2:888/405) in immediate mail (For this purpose create a little empty
file called "EMPTY.TXT". I assume that your statistic file name, de-
fined in FESetup - System - Filenames - Statistics Item (See 5.4.5.3)
has been defined as FAST.STA and the FAST.STA path is C:\FAST. Your
batch file will look like the following:
---------------------------------------------------------------------
FastEcho Stat -GABLKJ -O
FEUTIL Post C:\FAST\FAST.STA SysOp.332 -From "Reed Richards"
-To "All guys" -Subj "Monthly Statistics"
FastEcho Stat -GCIMX -RS -O
FEUTIL Post C:\FAST\FAST.STA #2 -From "Reed Richards"
-To "Richard Gizmo" -Subj "Monthly Statistics"
-Flags Pvt -Addr 1:323/323
FEUTIL Post C:\FAST\FAST.STA MYNETMAIL -From "Reed Richards"
-To "Bob Wisdom" -Subj "Monthly statistics"
-Flags Pvt -Addr 1:256/767
FEUTIL Post C:\FAST\EMPTY.TXT #2 -From "Reed Richards"
-To "Edwin Marshall" -Subj "C:\FAST\FAST.STA"
-Flags PVT+FILE+IMM -Addr 2:888/405
FastEcho Scan
---------------------------------------------------------------------
Be aware that the "FEUTIL Post" lines, in your batch file must
always be inserted in a single line although in this manual they are
shown upon multiple lines (to fit them in the available page space..
sorry). This batch file may also be automatically and periodically
invoked directly by your Mailer relying upon its external events.
7.10 - FEUTIL Import
-------------
As we mentioned several times throughout this manual, in your con-
figuration must exist one Main NetMail Directory called Primary NetMail
Area which is commomly defined for FastEcho and your mailer; and there
may exist one or more secondary NetMail area(s) defined by you in your
preferred messagebase. This, mostly, happens in BBS systems to allow
the interactive BBS users have access to it while, for point systems,
its definition is somewhat useless (Unless they wish to put the NetMail
messages that come from different networks in different Secondary
NetMail areas instead of having all NetMail messages gathered in a
single Secondary NetMail area; Nevertheless it may be useful only when
───────────────────────────────────────────────────────────────────────
- 137 -
FastEcho MANUAL - Using FEUtil -
───────────────────────────────────────────────────────────────────────
the point system is involved in more than one network with more than
one single Aka). When your incoming mail is tossed by means of the
FastEcho TOSS function, all the NetMail messages that may be contained
in the incoming mail bundles will never be directly tossed in your
secondary NetMail area but will always be left in the primary for
further processing or routing. To obtain that NetMail messages
addressed to you or to the interactive BBS users can be imported in
your Secondary NetMail area you must use the "FEUTIL Import" utilities.
Using "FEUTIL Import" you have some switches available to fine tune its
behavior in order to import only specified names or avoid the
importation of other specified names. In addition you may let "FEUTIL
Import" always imports all netmails addressed to any of your BBS users
directly: to do so you must switch to "Yes" the option "Include
USERS.BBS" in FESetup/FEUTIL parameters (see paragraph 5.4.9.6). Let's
now see these FEUTIL Import switches in detail.
7.10.1 - FEUTIL Import -Incl <file>
When the "FEUTIL Import" command is invoked with the "-Incl" switch
it looks for a file name, that must be specified in place of the <file>
item, in order to complete the correct command syntax. The target of
this command is to allow FEUTIL to import, from the Primary NetMail
Area to the Secondary one, only NetMail messages addressed to one of
the user listed in the file above mentioned; NetMails which are not ad-
dressed to the user listed therein will be, instead, completely ignored
and left in your Primary NetMail Area. Assuming that in the file
NIMP.TXT you have listed the names of the only NetMail message's ad-
dressee that you want FEUTIL to import in your Secondary NetMail area,
then your command will look like the following:
FEUTIL Import -Incl NIMP.TXT
7.10.2 - FEUTIL Import -Excl <file>
Like the switch previously seen, when the "-Excl" item is specified
invoking FEUTIL Import, the contents of the file specified in place of
the <file> item will be read from FEUTIL in order to let it know what
ase the NetMail message's adressees that you DON'T WANT imported from
the Primary NetMail area to the Secondary one. So, this option works to
avoid to importation of NetMail messages addressed to one of the users
specified in the <file> item, as opposed to the "-Incl" option we seen
in the previous paragraph. Assuming that in the file NONIMP.TXT you
have listed the names of the NetMail Message's adressees that you want
FEUTIL to avoid importing in your Secondary NetMail area, then your
command will look like the following:
FEUTIL Import -Excl NONIMP.TXT
7.10.3 - FEUTIL Import -FORCE
When this switch is used, FEUTIL will be bound to Import again the
already imported NetMails that remain in your Primary NetMail Area when
the switch "Keep NetMails" is active (See FESetup - Keep NetMails
5.4.9.6).
───────────────────────────────────────────────────────────────────────
- 138 -
FastEcho MANUAL - Using FEUtil -
───────────────────────────────────────────────────────────────────────
7.10.4 - Notes about FEUTIL
We have seen that both in "-Incl" and in the "-Excl" options there
must be specified a file containing a list of users. The format of this
file may be in plain ascii with an addressee name on each line or,
moreover, a convenient USERS.BBS file compatible with QBBS or RA2 stan-
dard, may be directly specified. The two items "-Incl" and "-Excl" (and
-FORCE too), could be specified in the "FEUTIL Import" command at the
same time, but, keep in mind that the "-Excl" always has priority over
the "-Incl". It means that if in the "-Excl" and in the "-Incl" file
only one name has been specified, then, a NetMail message addressed to
this name won't be imported (even if specified in the "-Incl" file).
Keeping the same sample file mentioned in paragraph 7.10.2 and 7.10.3,
then the complete command will be:
FEUTIL Import -Incl NIMP.TXT -Excl NOIMP.TXT
You may use the "FEUTIL import" command to import NetMail from all
your aka addresses separately. This can be done by defining different
NetMailbards for your different akas; in this case remember to set the
correct 'Use Aka' (See paragraph 5.5.3.1.9) which refers to the aka
address you wish to use for any NetMail area you define. May also
happen, that you define more than one NetMail area for the same aka,
well, in this case "FEUTIL import" will import NetMail messages relati-
ve to this aka in the NetMail area having the lowest read-security le-
vel (See: chapter 5.5.3.1.23.1).
8 - ENVIRONMENT VARIABLES
=====================
If specified, FastEcho may use several environment variables, each
one with its particular meaning. You can set an environment variable by
assigning it directly from your DOS prompt or automatically, inside a
batch file. For Example to assign the FD environment variable to point
to your FrontDoor System Directory, from your DOS prompt you must type:
C:> SET FD=C:\FD
The same line can be inserted in your Autoexec.bat, or other batch
file, to assign it automatically. Let's now see all the environment va-
riables supported by FastEcho and their meaning.
8.1 - FD, IM, DB environment variables
These environment variables may respectively point to the Front-
Door, InterMail, D'Bridge installation directories, according to the
Mailer you are currently using. Doing so, FastEcho will be able to aim
directly to the directory of your Mailer in order to find its confi-
guration files to correctly perform the Auto-Area-Create function (we
have seen in chapters 5.4.7.3 and 5.4.7.4). If the Auto-Area-Create
function is active and the mailer environment variable isn't set, then
FastEcho will search the mailer configuration files in the current di-
rectory.
───────────────────────────────────────────────────────────────────────
- 139 -
FastEcho MANUAL - Environment variables -
───────────────────────────────────────────────────────────────────────
8.2 - FE environment variable
The FE environment variable may point to the installation directory
of FastEcho where all the files relative to FastEcho reside. Setting
this environment variable allow you to start FastEcho anywhere in your
Hard Disk.
8.3 - FEUTMP environment variable
When FEUTIL performs the Pack operation upon JAM areas, it creates
some temporary files which, when the packing operation it completed,
will automatically be deleted. If you set this environment variable to
point to one particular directory (for example JAMTMP) it will be used
to store the JAM temporary files above mentioned. If this variable is
not specified, then FastEcho will use the actual directory to store the
JAM temporary files. By default, FEUTIL will create these files in the
current directory.
8.4 - HMBLOCK environment variable
When working in MultiLine/Multitasking environment it happens that
the same Hudson Message Base must be shared between two or more tasks.
As you certainly know, when writing, one file can be accessed by one
task at time because an indiscriminate write-access from more than one
task upon the same file may cause loss of data. So FastEcho must be
aware of it. When FastEcho operates with the "Share HMB" flag set (See:
chapter 5.4.7.9 of FESetup), while it's involved in the Hudson Message
Base processing, it checks, in the messagebase directory the existence
of a particular semaphores-file called "MBUNLOCK.NOW"; when this se-
maphore is found, it means that another program (RA), in another task
needs to write-access the same messagebase currently used (and locked)
by FastEcho. When FastEcho detects this semaphore it unlocks the mes-
sagebase, by setting it free, while the program in the other task per-
forms its requested write-operation.As soon as the concurrent program
finishes, FastEcho resumes and completes its previously suspended ope-
ration. This environment variable is needed in order to define the in-
terval of time in which FastEcho, when tossing the incoming mail,
should check for the MBUNLOCK.NOW semaphore presence. The time interval
must be specified in seconds. For example: SET HMBLOCK=20
This setting will tell FastEcho: "When you are involved in any
write operation on the Hudson Message Base, check every 20 seconds in
the MessageBase directory for the possible presence of the MBUNLOCK.NOW
semaphore. If you find it then suspend your operations, unlock the
messagebase and wait until the other program finishes. Resume your
process afterwards".
8.5 - TZUTC environment variable
This environment variable is needed in order to communicate to
FastEcho the time difference from the G.M.T. (Greenwich Mean Time) and
the time in your country. Its usage is the following:
SET TZUTC=[+/-]HHMM
Where the "+" or "-" signs represents the sign of difference
respect to the GMT and your country and HHMM represent the relative
───────────────────────────────────────────────────────────────────────
- 140 -
FastEcho MANUAL - Environment variables -
───────────────────────────────────────────────────────────────────────
time difference. For example If the time in your country is 06:00 PM
and the G.M.T. is 08:00 PM, the time amount difference is -2:00; In
this case you can set the TZUTC environment variable as follow:
SET TZUTC=-0200
8.6 - FEMAXMEM environment variable
By setting the FEMAXMEM environment variable you can now fix the
maximum amount of memory that FastEcho is allowed to use for outbound
PKT buffering. The usage syntax is the following:
SET FEMAXMEM=<memory size in Kilobytes>
The memory amount assigned to "FEMAXMEM" variable, refers to EMS-
type for the DOS version of FastEcho while for the DPMI version it
refers to extended memory. The default value (if FEMAXMEM is not
defined) for the OS/2 version is 4MB, all other versions will us all
available memory if FEMAXMEM is not defined.
8.7 - FEOPT environment variable
This is a particular environment variable that may be used to per-
manently set several runtime parameters for FastEcho, instead of speci-
fying them directly on the commandline when invoking FastEcho from the
DOS prompt. Its Usage is the following:
SET FEOPT=<flag>,<flag>,<...>
In several cases, in fact, using the FEOPT environment variable may be
more convenient than using the standard syntax that,for example may be:
FastEcho TOSS /<flag> /<flag>
FastEcho supports several FEOPT flags that may be used to cope with
a lot of circumstances. Let's now see them in detail.
8.7.1 - USEBIOS flag
To display its dialog screen, by default, FastEcho, uses the "di-
rect screen writes" method. By specifing this flag, instead, it will
always use the "BIOS-calls" method. Using "BIOS-calls" assures the
maximum compatibility but will result slower than the default method.
8.7.2 - NO386 flag
FastEcho and FEUTIL, to increase their performances, can automati-
cally take advantage from 386 or higher CPU. In case you come across
any problem using FastEcho, with machines equipped with such processors
then try to activate this flag and see if the problem has disappeared.
───────────────────────────────────────────────────────────────────────
- 141 -
FastEcho MANUAL - Environment variables -
───────────────────────────────────────────────────────────────────────
8.7.3 - NOEMS, NOXMS flags
FEUTIL, FastEcho and FESetup, can increase their potentiality by
using the Expanded Memory or Extended Memory available on your system
(see: 5.4.7.12, 5.4.3.3. and 5.4.4.11). If you wish to avoid this beha-
vior or you have some problems when FastEcho uses your EMS/XMS, then,
by using these flags, respectively, you will have the choice to disable
this feature.
8.7.4 - NOAFIX flag
We have seen, in the chapter 6.2 that, when FastEcho finishes
tossing the incoming mail, it automatically invokes its "built-in"
AreaFix processor. By using this flag you can, instead, make FastEcho
avoid this automatic AreaFix request processing after every "TOSS". Be
aware that, with this flag enabled, when you decide to process the
AreaFix request sent to your system by your downlinks you must
specifically invoke the FastEcho AreaFix processor by means of the
"FastEcho Afix" command.
8.7.5 - NOPACK flag
Normally, when FastEcho finishes exporting your outbound mail, by
means of the "FastEcho Scan" command, it creates one or more mail pa-
ckets with the .QQQ extension and, then, it archives them in an ARCmail
bundle ready to be sent or picked up. When this flag is activated,
these .QQQ mail packets will be left, as they are, in the outbound
directory. Furthermore, they will be correctly archived the next time
the "FastEcho Pack" function is called.
8.7.6 - NODUPES flag
When this flag is set as active, then the dupechecking feature
provided by FastEcho based on the dupe database will be disabled even
if they are all active in according with your FESetup settings. Use
this flag only if you really need it.
8.7.7 - NOEXPORT flag
The standard FastEcho procedure that FastEcho follows after every
"TOSS" operation is to detect all the areas joined by all your down-
links and to forward their mail to them. By using this flag, you can
temporarily change this standard FastEcho behavior, binding it to avoid
forwarding mail to your downlinks.
8.7.8 - NOSEENBY flag
FastEcho has the power to detect duplicated messages in several
ways: using its custom dupes database, using the messages' CRC check-
sum, usingthe SEEN-BY lines and using the MSGID kludge. By using this
switch you can compel FastEcho to ignore the SEEN-BY lines when it
checks for duplicates. Be aware that, if you disable this FastEcho
feature, your outgoing mail will be exported even if the target system
is already listed in the SEEN-BY lines.
───────────────────────────────────────────────────────────────────────
- 142 -
FastEcho MANUAL - Environment variables -
───────────────────────────────────────────────────────────────────────
8.7.9 - NOMSGID flag
Like the flag seen in the previous paragraph, this flag can disable
one standard FastEcho dupechecking feature. When this flag results ac-
tive, FastEcho will ignore the MSGID kludge contents when it checks for
duplicated messages; it will re-calculate a message header checksum
instead.
8.7.10 - NOAUTOFAIL flag
FastEcho has some automatic security features in order to avoid any
sharing violations happening when running in Multiline/Multitasking en-
vironments. Normally, when FastEcho senses that a sharing violation oc-
curs, it automatically stops its execution. By setting this flag acti-
ve, instead, you will bind it to ignore any FastEcho "sharing viola-
tion" automatic failure.
8.7.11 - RDEBUG flag
When using the NetMail-Packer-Router "FastEcho Pack" command with
the -R<file> switch (see: chapter 6.4.2), you can also rely upon this
very helpful flag. By enabling the RDEBUG flag, in fact, you can check
the functionalities of all the statements you inserteded inside the
ROUTE.FE files by logging all the relating debug information in your
main log file.
8.7.12 - STRIPTEAR flag
This flag acts upon the standard tearline normally inserted in eve-
ry message. When this flag is activated, in fact, FastEcho will strip
the tearline if it is able to find it in your messages; so they will
result in having only the "* Origin" line. (For further information
about the tearline meaning, see paragraphs 5.4.7.1 and 5.4.7.2).
8.7.13 - PACKONE flag
By using this flag, you will bind FastEcho to only call the com-
pression programs with one mail packet (.PKT) each time instead of cal-
ling them with as many mail packets as possible. This doesn't apply to
compression programs with a 'List' prefix set up.
8.7.14 - SHOWCURSOR flag
By setting this flag you will bind FastEcho to show a blinking
cursor, in addition to the normal highlighted box, while working with
FESetup configuration utility.
8.7.15 - NOLIMIT flag
When used, the NOLIMIT flag will disable FastEcho toss from che-
cking the "Minimum packet size" setting.
───────────────────────────────────────────────────────────────────────
- 143 -
FastEcho MANUAL - Environment variables -
───────────────────────────────────────────────────────────────────────
8.7.16 - NORES flag
FastEcho is capable to resolve the paths it founds in ECHOMAIL.JAM
when comparing them with the paths of the JAM areas settled by means of
FESETUP area configuration (AKA truename function). This functionality
can be disabled simply by using the NORES flag.
8.7.17 - NOERREP flag
FastEcho has the ability to report to the sysop several errors
occourred while it processes mail. By Default the report is
automatically generated and addressed to the SysOp in a NetMail message
but you can disable this feature with the NOERREP flag.
8.7.18 - ZONEGATE flag
When your system acts as outbound zonegate you may need to strip
all the SEEN-BY information present in your echomail for all messages
addressed out-of-zone. FastEcho is capable to do that simply by
enabling this feature (which is disabled by default). This can be done
by using the flag ZONEGATE in FEOPT. In any case FastEcho acts as an
inbound-zone-gate, which means SEEN-BYs will be stripped when
processing EchoMail coming from another zone.
.-.-.
FastEcho TOSS /NODUPES /NOAFIX
Or, alternatively, you can set, directly or in your autoexec.bat
file, the environment variable FEOPT in this way:
SET FEOPT=NODUPES,NOAFIX
and, then, start the FastEcho TOSS normally without any trailing flag.
───────────────────────────────────────────────────────────────────────
- 144 -
FastEcho MANUAL - Errorlevels -
───────────────────────────────────────────────────────────────────────
9 - ERRORLEVELS
===========
When FastEcho terminates its tasks, it exit to DOS feeding back an
errorlevel in order to communicate to the batch file what action it has
to take according to the operation that FastEcho has performed or if
some errors occoured. You must, of course, adjust your batch file in
conformity with the errorlevels given back from FastEcho. Here below is
a report of the complete errorlevel list.
┌──────────┬────────────────────────────────────────────────────────┐
│ERRORLEVEL│ M E A N I N G S │
├──────────┼────────────────────────────────────────────────────────┤
│ 0 │FastEcho has found that there is nothing to do on your│
│ │messagebase nor are there any mail packets to process.│
│ │The same errorlevel means that FastEcho has terminated│
│ │its execution with no errors. │
├──────────┼────────────────────────────────────────────────────────┤
│ 1 │FastEcho has terminated its execution after NetMail or│
│ │EchoMail has been Packed or Scanned. │
├──────────┼────────────────────────────────────────────────────────┤
│ 3 │FastEcho has sensed some irregularity in your registra-│
│ │tion key file. │
├──────────┼────────────────────────────────────────────────────────┤
│ 10 │FastEcho/FEUTIL have imported one or more NetMail mess. │
├──────────┼────────────────────────────────────────────────────────┤
│ 11 │FastEcho has imported one or more EchoMail-only mes-│
│ │sages (FastEcho TOSS). │
├──────────┼────────────────────────────────────────────────────────┤
│ 12 │FastEcho has imported both EchoMail and NetMail mes-│
│ │sages. │
├──────────┼────────────────────────────────────────────────────────┤
│ 245 │FastEcho isn't able to extract an archive. Your Hard│
│ │Disk Drive is probably Full. │
├──────────┼────────────────────────────────────────────────────────┤
│ 246 │FastEcho has detected that you manually interrupted its│
│ │execution. │
├──────────┼────────────────────────────────────────────────────────┤
│ 247 │FastEcho can't write a NetMail File │
├──────────┼────────────────────────────────────────────────────────┤
│ 248 │FastEcho can't write a MsgBase File │
├──────────┼────────────────────────────────────────────────────────┤
│ 249 │FastEcho can't create a .PKT file │
├──────────┼────────────────────────────────────────────────────────┤
│ 250 │You have used a wrong switch │
├──────────┼────────────────────────────────────────────────────────┤
│ 251 │HMB file size mismatch │
├──────────┼────────────────────────────────────────────────────────┤
│ 252 │FastEcho is unable to lock the messagebase. │
├──────────┼────────────────────────────────────────────────────────┤
│ 253 │FastEcho has detected that your HMB messagebase has rea-│
│ │ched its limits and now it needs to be purged and packed│
├──────────┼────────────────────────────────────────────────────────┤
│ 254 │FE hasn't enough memory to run │
├──────────┼────────────────────────────────────────────────────────┤
│ 255 │General error │
└──────────┴────────────────────────────────────────────────────────┘
───────────────────────────────────────────────────────────────────────
- 145 -
FastEcho MANUAL - Semaphores -
───────────────────────────────────────────────────────────────────────
10 - SEMAPHORE FILES
===============
FastEcho has the power to handle, and create too, several semaphore
files. Each semaphore has its specifical meaning and purpose. In the
following table are reported all the semaphore-files handled by Fast-
Echo with their purpose. Refer to this table whenever you need explana-
tion about them.
┌────────────┬──────────────────────────────────────────────────────┐
│ FILENAME │ P U R P O S E S │
├────────────┼──────────────────────────────────────────────────────┤
│NEWAREAS.FE │When this semaphore is present it means that the Fast-│
*│ │Echo TOSS function has added new areas to the FastEcho│
│ │setup thanks to the AutoAreaCreate Feature. │
├────────────┼──────────────────────────────────────────────────────┤
*│PACKHMB.FE │FastEcho TOSS has sensed that your Hudson MsgBase is │
│ │going out of its limits and needs to be purged/packed.│
├────────────┼──────────────────────────────────────────────────────┤
│MBUNLOCK.NOW│The FastEcho TOSS function will check for this file in│
│ │the messagebase directory and will temporarily unlock │
│ │the Hudson Message Base it was found/updated. │
├────────────┼──────────────────────────────────────────────────────┤
│FEBUSY.<lne>│This semaphore, created by FE,FEUTIL, FESetup & FEUTIL│
│ │allow the suspension of their execution when a pre-│
│ <lne>=line │vious FEBUSY.* semaphore will be found in the sema-│
│ │phore or system directory. This is done to avoid that│
│ │two or more copies of FastEcho or FEUTIL run at the│
│ │same time. │
├────────────┼──────────────────────────────────────────────────────┤
│FEPACK.REC │This semaphore is created by FastEcho when interrupted│
│ │or hanged while archiving ARCMAIL. Thanks to this se-│
│ │maphore FastEcho is capable to recover the previous-│
│ │ly failed mail forwarding session without problems. │
├────────────┼──────────────────────────────────────────────────────┤
│FDRESCAN.NOW│This semaphore will be created/updated if new NetMail│
#│FMRESCAN.NOW│(included file-attaches ecc.) have been created and│
│ │in FrontDoor Environment the "Force Mailer Rescan" op-│
│ │tion is turned on. │
├────────────┼──────────────────────────────────────────────────────┤
#│IMRESCAN.NOW│Same as above, but for InterMail environment │
│IERESCAN.NOW│ │
├────────────┼──────────────────────────────────────────────────────┤
#│DBRIDGE.RSN │Same as above, but for D'Bridge environment │
├────────────┼──────────────────────────────────────────────────────┤
#│DBRIDGE.NMW │This semaphore will be created by FastEcho TOSS when │
│ │new NetMail has ben received and you are working in │
│ │D'Bridge environment. │
├────────────┼──────────────────────────────────────────────────────┤
#│DBRIDGE.EMW │This semaphore will be created by FastEcho TOSS when │
│ │new EchoMail has been received and you are working in │
│ │D'Bridge environment. │
└────────────┴──────────────────────────────────────────────────────┘
(*) - Semaphores created in the FastEcho system directory (I.E. where
you installed it and where FastEcho.CFG is read from) Your batch
file may check for these file only aiming there.
(#) - Semaphores created/updated only if you have defined the "Semapho-
re directory in FESetup (see: paragraph 5.4.4.8).
───────────────────────────────────────────────────────────────────────
- 146 -
FastEcho MANUAL - Files created or used by FastEcho -
───────────────────────────────────────────────────────────────────────
11 - FILES CREATED OR USED BY FastEcho
=================================
Here below is summarized the complete set of files created and/or
used by FastEcho. Refer to this table everytime you need information
about FastEcho Files: What they do, What purposes they have, when you
need them.
┌────────────┬──────────────────────────────────────────────────────┐
│ FILENAME │ P U R P O S E S │
├────────────┼──────────────────────────────────────────────────────┤
│FastEcho.CFG│This is the main FastEcho configuration file. Here all│
│ │your FESetup setting are permanently stored. │
├────────────┼──────────────────────────────────────────────────────┤
│FastEcho.DAT│In this file FastEcho stores all your daily mail mo- │
│ │vement in order to create the statistic file when you │
│ │request it using the "FastEcho Stat" command. │
├────────────┼──────────────────────────────────────────────────────┤
│FastEcho.DUP│In this file FastEcho will keep track of all your al- │
│ │ready processed mail in order to search for possible │
│ │duplicated message in your incoming mail packets. │
├────────────┼──────────────────────────────────────────────────────┤
│FTSCPROD.FE │This file contains a list of all products having a│
│ │FTSC product code. This product code will automatical-│
│ │ly show up when FastEcho processes the inbound mail│
│ │packets. │
├────────────┼──────────────────────────────────────────────────────┤
*│IMPORT.XYZ │This is a plain ascii file containing a list of areas │
│ │to which messages were imported the last time you exe-│
│ │cuted the TOSS operation. This file will then be used,│
│ │by default, from the FEUTIL link function. │
├────────────┼──────────────────────────────────────────────────────┤
*│IMPORT.JAM │Same as above, but for JAM areas │
├────────────┼──────────────────────────────────────────────────────┤
*│IMPORT.SQ │Same as above, but for Squish areas │
├────────────┼──────────────────────────────────────────────────────┤
*│IMPORT.SDM │Same as above, but for Fido/*.MSG areas │
├────────────┼──────────────────────────────────────────────────────┤
│NOLINK.FE │These files aree strictly related to Fido/*.MSG areas.│
│NOPURGE.FE │If one (or more) of these files is present in a Fido │
│NOPACK.FE │*.MSG directory, then FEUTIL won't process the indica-│
│ │ted function even if it's specifically invoked. │
└────────────┴──────────────────────────────────────────────────────┘
(*) - These IMPORT files will be used (and then deleted afterwards) by
several FEUTIL functions. If any of these files are already pre-
sent, then FastEcho TOSS appends its data to them (the areas in
which the new tossed mail has been imported to).
───────────────────────────────────────────────────────────────────────
- 147 -
FastEcho MANUAL - Batch file examples -
───────────────────────────────────────────────────────────────────────
12 - BATCH FILES EXAMPLE
===================
Here below is reported a batch file example to give you a simple
outline about how to run FastEcho and FEUTIL in batch mode. I assume
that you are using FrontDoor as Mailer and you have configured it in
order to exit with the errorlevel 110 when any mail is received.
rem <- CALL YOUR MAILER
:START
cd c:\fd
fd
rem <- If your mailer recei-
rem ves EchoMail or net-
rem mail it exit with an
rem errorlevel of 110
if errorlevel=110 goto TOSS
[...]
if errorlevel=??? goto ??? other errorlevel and
if errorlevel=??? goto ??? other label to run
if errorlevel=??? goto ??? your BBS (if any)
[...]
goto START
rem
rem <-TOSS INCOMING MAIL
:TOSS
cd c:\fast\
rem <- Process the incoming
rem mail bundles with the
rem Carbon Copy function
rem activated.
FastEcho toss -C
rem <- If the packhmb sema-
rem phore is detected
rem then you must go to
rem MAINTAIN procedure.
if exist c:\fast\packhmb.fe goto MAINTAIN
rem <- Otherwise follow with
rem the aftertoss proced.
rem
rem <- DETECT THE TYPE OF
rem MAIL RECEIVED
:AFTERTOSS
rem <- Detect the exit error-
rem level given back
rem from FastEcho toss and
rem choose the right des-
rem tination label
rem
rem <-12=Echo/NetMail rcvd
rem process both.
if errorlevel 12 goto EchoMail
rem <-11=EchoMail received
rem process both.
if errorlevel 11 goto EchoMail
rem <-10=NetMail received
rem pack only NetMail.
───────────────────────────────────────────────────────────────────────
- 148 -
FastEcho MANUAL - Batch file examples -
───────────────────────────────────────────────────────────────────────
if errorlevel 10 goto PACKNetMail
rem
rem <-if the errorlevel is
rem different from 12,11
rem or 10, restart FD
goto START
rem
rem <-PROCESS EchoMailS
:EchoMail
rem <-Process EchoMail by
rem sorting (with backup)
rem and linking the messa-
rem gebase (ignoring the
rem IMPORT.??? file)
FEUTIL sort -b
FEUTIL link -i
rem <-When finished restart
rem FrontDoor
goto START
rem
rem <-PACK/ROUTE NetMail
:PACKNetMail
rem <-By using the advanced
rem Route.fe method.
FastEcho pack -rROUTE.FE
rem <-When finished restart
rem FrontDoor
goto START
rem
rem <-MAINTAIN MESSAGEBASE
rem
rem <-When the HMB excedes
rem its limits the batch
rem does it automatically
:MAINTAIN
rem <-Purge the messagebase
FEUTIL Purge
rem <-And then remove physi-
rem cally the messages
rem marked for deletion.
FEUTIL Pack -Force -Delete
rem <-Delete the overflow
rem semaphore.
del c:\fast\packhmb.fe
rem <-When finished return
rem to the TOSS operation
goto TOSS
-------------------------------------------------------------------
This batch file must be tuned, of course, in accordance with your
specifical system configuration.
───────────────────────────────────────────────────────────────────────
- 149 -
FastEcho MANUAL - Differences between DOS & DPMI versions
───────────────────────────────────────────────────────────────────────
13 - DIFFERENCES BETWEEN DOS AND 16 BIT DPMI VERSIONS
================================================
The FastEchoDPMI version works in protected mode giving you some
extra performance. There are, of course, some operational differences
between the 16 bit version and the DOS on; further you must take care
about some precautionary measures. Altogether, if your systm can rely
upon enough memory availability, using the new DPMI versionyou may ob-
tain considerably advantages.
13.1 - DPMI Version Requirements
If you want run the DPMI 16 bit version of FastEcho you will need
to have RTM.EXE and DPMI16BI.OVL either in your installation directory
or in a directory defined in your PATH environment variable. If you use
another DPMI server rather than the included one (for example OS/2 or
QDPMI) you will avoid the following compatibility problems.
13.2 - Compatibility problems using the included DPMI server
As told before, using the included DPMI server you may run into
some compatibility problems:
- PKZip 2.04 needs the '-3' switch (without quotes) or it will hang
occasionally; further, in certain environments it might be a good
idea to disable the PKZip's DPMI support with the '-)' switch
(without quotes).
- .EXEs hang when running under DESQview (works fine with QDPMI)
13.3 - Precautions using the DPMI version
When using the DPMI 16 bit version of FastEcho you must always take
care of the following suggestions:
- You cannot call external programs which make use of their own DOS
extender like DOS4GW. Alternatively you can execute them before,
or after, you run FASTECH16.EXE rather than define them in the
'After Unpack' or 'Before Pack' items of FESetup.
- You need a certain amount of free memory, both conventional and
extended, otherwise the program will be very slow, because it
continuosly has to swap the overlays. When short in memory it
further may occasionally hang. The amount of memory nedeed de-
pends, of course, on your personal FastEcho setup. If you notice
that FastEcho takes more than 10-20 seconds before the program
logo appear when you call it manually, you can be almost sure
that there isn't enough memory. Furthermore, if you are low on
memory, FastEcho/16 will probably not be able to call the com-
pression programs returning an error code (or may even occasio-
nally hang).
───────────────────────────────────────────────────────────────────────
- 150 -
FastEcho MANUAL - Differences between DOS & DPMI versions
───────────────────────────────────────────────────────────────────────
- you can't call the executables directly from an OS/2 session (if
you for any reason don't want to use the OS/2 executables), you
have for example add the following to the .CMD you're using:
COMMAND.COM /C FASTEC16 TOSS -C
Calling them within a DOS session under OS/2 works flawlessly, of
course.
13.4 - Differences between the DOS and protected mode versions
The main differences between the DOS and protected mode version of
FastEcho are synoptically syntetized below:
- Using the 16 bit version you can rely on a plenty of free memory
- The 16 bit version is a bit slower in several places as regards
the DOS one. That's because it has to switch from protected mode
to real mode every time it calls DOS interrupts.
- The 16 bit version allows up to 262000 dupe records but in needs
more memory than the real mode version for the same number of
records but it is a lot faster than the EMS and XMS support.
13.5 - DPMI Runtime module options
Through the RTM environment variable you can set several option for
the 16 bit version of FastEcho fine tuning its behaviour in according
with your needs. The setting sintax is, as usual:
SET RTM=[OPTION nnnn [OPTION nnnn [...]]]
Here below are summarized and described all the options availables.
EXTLEAVE nnnn :Allows you to leave at least nnnn Kb of free Exten-
ded memory.
EXTMAX nnnn :Prevent RTM to use more than nnnn Kb of Extended
Memory.
EXTMIN nnnn :Bind RTM to exit if it senses that less than nnnn Kb
of Extended memory are available.
REALLEAVE nnnn:Bind RTM to leave at least nnnn _segments_ of free
conventional memory during its operation.
REALMAX nnnn :Has the same meaning of EXTMAX, but for real mode
memory _segments_, 1 segment = 16 bytes.
REALMIN nnnn :Has the same meaning of EXTMIN, but for real mode
memory _segments_, 1 segment = 16 bytes.
Example:
SET RTM=EXTMAX 2048 REALLEAVE 8192
By setting these options, RTM starts its operation binding itself
to to use more than 2048 Kilobytes of Extended Memory and leaving 8192
_segments_ of conventional memory free.
───────────────────────────────────────────────────────────────────────
- 151 -
FastEcho MANUAL - A p p e n d i x e s -
───────────────────────────────────────────────────────────────────────
Appendix (A) - Zone/Net/Node/Point
===================
When talking about four dimension addresses we mean a pratical
method to conveniently identify any item that constitutes a NetWork,
its task and its geographical location. A typical 4D address is compo-
sed of four items; for example see the following address: 2:332/317.2
┌───────────────┐
│This address │ NET─┐ ┌─NODE
│identifies the│ v v
│first point of│ ┌─┐ ┌───┐ ┌───┐ ┌─┐
│the 17.th node│ ZONE─────>│2│:│332│/│317│.│1│<─────POINT
│of the Hub 300 │ └─┘ └─┬─┘ └─┬─┘ └─┘
│located in the│ ┌────┘ └────┐
│2.nd Net of re-│ ┌───┴──┐ ┌───┴───┐
│gion 33. │ │ │ │ │
└───────────────┘ ┌┴─┐ ┌┴┐ ┌─┴─┐ ┌─┴┐
REGION<─────┤33│ │2│ │300│ + │17├──────> 17.th NODE
└──┘ └┬┘ └─┬─┘ └──┘
NET NUMBER<─────────────┘ └───────────────> HUB(*)
* The HUB clause is valid for Z2 only.
┌────────────────────────────────────────────────────────────────────┐
│ PARTS OF A 4 DIMENSION NETWORK ADDRESS │
├─────────┬──────────────────────────────────────────────────────────┤
│ I T E M │ D E S C R I P T I O N │
├─────────┼──────────────────────────────────────────────────────────┤
│ ZONE │ The "Zone" represents a large geograhical area such as │
│ │ all Europe or North America. Actually the allocated Fi- │
│ │ doNet Zones are six: │
│ │ 1 North America and Canada │
│ │ 2 Europe │
│ │ 3 Australia, Tasmania, NewZealand │
│ │ 4 Latin America │
│ │ 5 Africa │
│ │ 6 Asia │
├─────────┼──────────────────────────────────────────────────────────┤
│ REGION │ The region is a geographical area smaller than the │
│ │ "Zone",It can be assimilated to a country or, in case of │
│ │ very big countries, to a part of it. As you certainly │
│ │ have already understood, a Zone is constituted by a set │
│ │ of regions. │
├─────────┼──────────────────────────────────────────────────────────┤
│ NET │ A Net is, normally, a set of local systems that resides │
│ │ in a city or in its district or suburbia. A set of nets │
│ │ constitutes one region. │
├─────────┼──────────────────────────────────────────────────────────┤
│ NODE │ A single system within a net, useless, at this point,men-│
│ │ tion that a set of nodes constitutes one net. │
├─────────┼──────────────────────────────────────────────────────────┤
│ POINT │ A point is a single system subordinated to a node. A │
│ │ point system is assimilated to a user logging on to a │
│ │ node using a terminal program, with the main difference │
│ │ being that a point performs most of its activities off- │
│ │ line by using smart software to collect and transmit │
│ │ mail to the node to which belongs. │
└─────────┴──────────────────────────────────────────────────────────┘
───────────────────────────────────────────────────────────────────────
- 152 -
FastEcho MANUAL - A p p e n d i x e s -
───────────────────────────────────────────────────────────────────────
Appendix (B) - Message kludges
===============
The, so named, message kludges, are special control lines, having a
'^A'(01h) as first character of the line. In the table below will be
reported the most used message kludges with a brief explanation about
their meaning:
┌────────────────────────────────────────────────────────────────────┐
│ M E S S A G E K L U D G E S │
├─────────┬───────────┬──────────────────────────────────────────────┤
│ I T E M │ REFERENCE │ D E S C R I P T I O N │
├─────────┼───────────┼──────────────────────────────────────────────┤
│ CHARSET │ FSC-0050 │ Hig-bit characters normalization. This klud-│
│ │ FSC-0054 │ ge has a parameter that specifies the set u- │
│ │ │ sed by the message sender. │
├─────────┼───────────┼──────────────────────────────────────────────┤
│ CHRC │ FSC-0054 │ Characters font changer. The parameter spe- │
│ │ │ cified after this kludge specifies the font │
│ │ │ and the character attributes used by sender │
├─────────┼───────────┼──────────────────────────────────────────────┤
│ DOMAIN │ FSC-0038 │ This kludge is used in the Inter-Domain mes- │
│ │ │ sages in order to solve the problem of the │
│ │ │ mail having to cross the domain boundaries. │
├─────────┼───────────┼──────────────────────────────────────────────┤
│ FLAGS │ FSC-0053 │ Used only in NetMail messages. When used it │
│ │ │ provides special non-standard attributes that│
│ │ │ may be customized to be understood between │
│ │ │ programs that support them. │
├─────────┼───────────┼──────────────────────────────────────────────┤
│ FMPT │ FTS-0001 │ Used only in NetMail messages and only if│
│ │ │ message has been sent from a point system. It│
│ │ │ identifies the originator point number. │
├─────────┼───────────┼──────────────────────────────────────────────┤
│ INTL │ FTS-0001 │ Used only in NetMail message. This is a klud-│
│ │ │ ge that specifies when a NetMail message has │
│ │ │ to cross from one Zone to another. │
├─────────┼───────────┼──────────────────────────────────────────────┤
│ MSGID │ FTS-0009 │ Is a NetMail/EchoMail kludge that having the │
│ │ │ task to univocally identify a message. This │
│ │ │ kludge is mostly used to obtain reply-link │
│ │ │ and duplicated message seeking. │
├─────────┼───────────┼──────────────────────────────────────────────┤
│ Original│ * none * │ It's a kludge generated only by the FrontDoor│
│ │ │ folder manager (FM) when it generates carbon │
│ │ │ copies (it marks the original one) │
├─────────┼───────────┼──────────────────────────────────────────────┤
│ PATH │ FTS-0004 │ It identifies the path followed by a message │
│ │ │ in order to reach your system. It can be used│
│ │ │ to check for net-routing errors. It supports │
│ │ │ only 2D addressing. │
├─────────┼───────────┼──────────────────────────────────────────────┤
│ PTH │ * none * │ It performs the same task as the PATH kludge │
│ │ │ but is 5D capable. │
└─────────┴───────────┴──────────────────────────────────────────────┘
───────────────────────────────────────────────────────────────────────
- 153 -
FastEcho MANUAL - A p p e n d i x e s -
───────────────────────────────────────────────────────────────────────
┌────────────────────────────────────────────────────────────────────┐
│ M E S S A G E K L U D G E S │
├─────────┬───────────┬──────────────────────────────────────────────┤
│ I T E M │ REFERENCE │ D E S C R I P T I O N │
├─────────┼───────────┼──────────────────────────────────────────────┤
│ PID │ FSC-0046 │ This kludge reports the information about │
│ │ │ the first mail processor that treated the │
│ │ │ message in which it was inserted. │
├─────────┼───────────┼──────────────────────────────────────────────┤
│ REPLY │ FTS-0009 │ Identifies that this message is a reply to │
│ │ │ another message.The Reply kludge reports the │
│ │ │ MSGid contents of the message it has replied │
│ │ │ to in order to allow the creation of the re- │
│ │ │ ply link (see: chapter 7.2 for further info) │
├─────────┼───────────┼──────────────────────────────────────────────┤
│ SEEN-BY │ FTS-0004 │ This Kludge may, or not, have the ^a charac- │
│ │ │ ter at its begining, in any case it is use- │
│ │ │ ful to let Mail processors find duplicated │
│ │ │ messages or EchoMail routing errors. It Pra- │
│ │ │ tically lists all the system which have al- │
│ │ │ ready seen the message. │
├─────────┼───────────┼──────────────────────────────────────────────┤
│ TOPT │ FTS-0001 │ This kludge is used in NetMail messages only │
│ │ │ and it identifies the number of points which │
│ │ │ this message is addressed to. │
├─────────┼───────────┼──────────────────────────────────────────────┤
│ NPD │ │ Acronym for "Non Proportional Display". It's │
│ │ │ aim is to tell to mail editors working in GUI│
│ │ │ (Graphics User interface) environments (Such │
│ │ │ as Windows and OS/2 Program Manager) to use a│
│ │ │ non proportional (fixed pitch) font to dis- │
│ │ │ play the message. This kludge is mainly used │
│ │ │ for list created by AreaFix or other program-│
│ │ │ generated report. │
└─────────┴───────────┴──────────────────────────────────────────────┘
───────────────────────────────────────────────────────────────────────
- 154 -
FastEcho MANUAL - A p p e n d i x e s -
───────────────────────────────────────────────────────────────────────
Appendix (C) - Message Attributes
==================
The message attributes specify, mostly, the messages aim and/or the
message status, furthermore, them determines how the mailer must treat
the outgoing NetMail messages and how your editor must handle the inco-
ming NetMail messages.. There are a lot of message attributes, standard
or not. In the table below the most common of them will be summarized.
┌────────────────────────────────────────────────────────────────────┐
│ M E S S A G E A T T R I B U T E S │
├───────────┬────────────────────────────────────────────────────────┤
│ ATTRIBUTE │ D E S C R I P T I O N │
├───────────┼────────────────────────────────────────────────────────┤
│ ATT │ Means that the present NetMail message has a file at- │
│ │ tached to it. The path and file specification of the │
│ │ file to be sent must always be specified in the messa- │
│ │ ge subject. The message text may contain other infor- │
│ │ mations too. │
├───────────┼────────────────────────────────────────────────────────┤
│ CRA │ Crash or High-Priority mail. The messages having this │
│ │ attribute set, bypass any routing statement and are, │
│ │ usually, sent directly to the addressee system. │
├───────────┼────────────────────────────────────────────────────────┤
│ DIR │ This means "Direct". the presence of this attribute in │
│ (*) │ te in a NetMail message implies that it can be sent │
│ │ to this system directly (avoiding to go through in-│
│ │ termediary systems). If, for example, a NetMail messa-│
│ │ ge has the DIR and the HOLD attribute together, it re-│
│ │ quires that only the destination system (points inclu-│
│ │ ded) calls your system to be able to pickup their mail.│
├───────────┼────────────────────────────────────────────────────────┤
│ FRQ │ File/Request. When a NetMail message having this attri-│
│ │ bute is sent, then the addressee system will consider │
│ │ it as a request to send one or more files to the reque-│
│ │ sting system. The files requested must be indicated in │
│ │ the message subject. A NetMail message having this at- │
│ │ tribute set, must always be sent directly and never │
│ │ routed. │
├───────────┼────────────────────────────────────────────────────────┤
│ HLD │ This means "Hold". If a NetMail message has this attri-│
│ │ bute set, then the mailer doesn't route or send it un-│
│ │ less the addressee system calls yours. In case of net-│
│ │ mail message addressed to a point system, it will be │
│ │ delivered through its boss but only if the boss calls │
│ │ your system (this doesn't apply if the message also │
│ │ has the DIR status (seen before). │
├───────────┼────────────────────────────────────────────────────────┤
│ IMM │ When a NetMail message has the "IMM" (Immediate) attri-│
│ (*) │ bute set, then it will be sent immediately, ignoring │
│ │ any mailer restriction and/or qualification. So it │
│ │ will force the mailer to call the destination system │
│ │ to give it your mail. │
└───────────┴────────────────────────────────────────────────────────┘
───────────────────────────────────────────────────────────────────────
- 155 -
FastEcho MANUAL - A p p e n d i x e s -
───────────────────────────────────────────────────────────────────────
┌────────────────────────────────────────────────────────────────────┐
│ M E S S A G E A T T R I B U T E S │
├───────────┬────────────────────────────────────────────────────────┤
│ ATTRIBUTE │ D E S C R I P T I O N │
├───────────┼────────────────────────────────────────────────────────┤
│ K/S │ It's the Kill/Sent attributes. It does mean that the │
│ │ NetMail message,having the Kill/Sent attributes set, │
│ │ will be automatically deleted as soon it will be sent │
│ │ or routed to the addressee system. │
├───────────┼────────────────────────────────────────────────────────┤
│ KFS │ This attributes means "Kill-File-Sent". It's only used │
│ (*) │ in NetMail messages that already have the ATT attribu- │
│ │ te (seen before), in order to let your mailer delete │
│ │ the original attached file as soon as it's succesful- │
│ │ ly sent to the addressee system. │
├───────────┼────────────────────────────────────────────────────────┤
│ LOC │ This is the "Local" message attribute. Normally all │
│ │ your NetMail/EchoMail message will have this attribute │
│ │ set by default. │
├───────────┼────────────────────────────────────────────────────────┤
│ LOK │ This is the "Locked" attribute. One locked message can │
│ (*) │ not be deleted nor purged and not sent at all. It is │
│ │ useful in case you want to preserve one or more impor-│
│ │ tant messages from manual deletion or from automatic │
│ │ purging/packing routinges.This attributes can only be │
│ │ set upon Old-Fido-Style *.MSG messages. │
├───────────┼────────────────────────────────────────────────────────┤
│ PVT │ A message having this attribute is considered as priva-│
│ │ te. This means that, theoretically, it could be read │
│ │ only by its addressee and not by anyone else. Normally │
│ │ ly only the NetMail message may have this attribute. │
├───────────┼────────────────────────────────────────────────────────┤
│ PGM │ It means that the message having this attribute set has│
│ │ been automatically generated by a program. │
├───────────┼────────────────────────────────────────────────────────┤
│ RCV │ When a NetMail message has this attribute does mean │
│ │ that it has already been received and read by its ad- │
│ │ dressee. │
├───────────┼────────────────────────────────────────────────────────┤
│ RRQ │ This is a request for a return receipt from the ad-│
│ │ dressee system. When a NetMail message having this at-│
│ │ tribute is sent, then the destination system will gene-│
│ │ rate (if capable) a confirmation receipt automatical-│
│ │ ly addressed to the original message sender in order │
│ │ to confirm that the NetMail message has reached its │
│ │ correct destination. │
├───────────┼────────────────────────────────────────────────────────┤
│ RRC │ This is the flag automatically set by the mail proces- │
│ │ sor or mailer (capable of handling the NetMail messa- │
│ │ ges having the RRQ flag) when they produces their "Re- │
│ │ turn Receipt Confirmation" as answer to the message │
│ │ having the "Return Receipt reQuest" attribute set. │
├───────────┼────────────────────────────────────────────────────────┤
│ SNT │ Mean that the message, having this attribute, has al- │
│ │ ready been sent or routed towards its destination. │
└───────────┴────────────────────────────────────────────────────────┘
───────────────────────────────────────────────────────────────────────
- 156 -
FastEcho MANUAL - A p p e n d i x e s -
───────────────────────────────────────────────────────────────────────
┌────────────────────────────────────────────────────────────────────┐
│ M E S S A G E A T T R I B U T E S │
├───────────┬────────────────────────────────────────────────────────┤
│ ATTRIBUTE │ D E S C R I P T I O N │
├───────────┼────────────────────────────────────────────────────────┤
│ TFS │ This attribute involves mostly the ARCmail attaches. │
│ (*) │ It implies that the ARCmail bundle attached to this │
│ │ NetMail message,after being sent to the addressee sys- │
│ │ tem has to be truncated to a file having a null- │
│ │ length size instead of deleted. Leaving this zero │
│ │ length file in your outbound directory may be useful │
│ │ for references. (A truncated file cannot be undeleted) │
├───────────┼────────────────────────────────────────────────────────┤
│ TRS │ This is the "in-Transit" attribute. A NetMail having │
│ │ this attribute is only transiting upon your system │
│ │ and was originated outside it. │
├───────────┼────────────────────────────────────────────────────────┤
│ UNS │ This attributes does mean "still Unsent". It normally │
│ │ can be located in the EchoMail/NetMail messages which │
│ │ haven't been exported from your messagebase. │
├───────────┼────────────────────────────────────────────────────────┤
│ URQ │ Means "Update Request". This is an attribute similar │
│ │ to the FRQ one (we mentioned above in this appendix. │
│ │ The only difference is that,in this case, the reques- │
│ │ ted file will be sent only if the file owned by the │
│ │ requester is older than the file owned by the system │
│ │ tem that accepts the Update Request. To perform the up-│
│ │ date request,in the Message Subject,the demandant must │
│ │ indicate the complete pathname and filename of the file│
│ │ that he wants be updated. │
└───────────┴────────────────────────────────────────────────────────┘
(*) These attibutes are extensions of the "FLAGS" kludge.
Appendix (D) - Technical Notes
===============
* The FTSC product-code for FastEcho is 0xAF (hex), 175 (dec).
* FastEcho can handle up to 1024 systems and 4096 areas.
* FastEcho can process EchoMail messages up to 64kB (512kB for the OS/2
version), depending on the settings in FESetup/Advanced Options
/Messagebuffer.
* The mail-packets created by FastEcho are compatible to FTS-0001, FTS-
0004 and FSC-0039, using the Type 2+ packet-header and supporting the
Capability Word. FastEcho will also recognize incoming FSC-0048 and
FSC-0045 (Type 2.2) mail-packets.
* Linefeeds are always stripped when processing mails, soft CR's are
treated as normal, valid characters.
* SEEN-BY lines and ^APATH kludges are created and updated.
───────────────────────────────────────────────────────────────────────
- 157 -
FastEcho MANUAL - A p p e n d i x e s -
───────────────────────────────────────────────────────────────────────
* SEEN-BY is used for duplicate prevention - if a system is already
listed in the SEEN-BY of an incoming message, FastEcho will not for-
ward that message to this system. [This does NOT apply to point-sys-
tems as the SEEN-BY are 2D only !]
* FastEcho can parse both SeaDog and Fido/Opus date-fields, it gene-
rates Fido/Opus-style dates when exporting EchoMail.
* FastEcho supports the RemoteAccess/FrontDoor Hudson-messagebase sha-
ring specifications and sharing of JAM and Squish messagebases.
* The dupechecking algorithm checks the ^MSGID kludge if available and
a header checksum if not. In order to store the maximum 131000 re-
cords in while tossing/scanning it needs 512kB of EMS or XMS memory.
* Outbound mail-packets generated by FastEcho have a .QQQ extension.
To compress them, FastEcho renames them to .PKT and adds 2 <NUL> by-
tes at the end of the packets. If any error occurs while running the
archiver, FastEcho will rename them back to .QQQ, so they may be com-
pressed in a further run of FastEcho.
* For a better performance, unlike other EchoMail processors, FastEcho
keeps the outbound mail-packets open while processing. Therefore to
run without error you must give FastEcho all the FILES=??? that are
necessary to have the packets for every system defined in the Node-
Manager simultaneously open.
* FastEcho supports the 4D addressing which BinkleyTerm 2.50+, Xenia,
McMail and other Binkley compatible mailers offer for points.
Futhermore it supports BinkleyTerm's 5D (domain) outbounds.
* FastEcho supports the '.BSY' files created by BinkleyTerm 2.50+ in
multiline-environments and will not compress mail for a system cur-
rently online.
* FastEcho supports the crc.`nn semaphore files FrontDoor 2.20/c crea-
tes in multiline-environments and will not compress mail for a system
currently online.
* FastEcho supports the Xnnnnnnn.nll semaphore files created by
InterMail 2.25 for checking if a system is currently online.
* FastEcho supports the RemoteAccess-Messagebase-Locking technique as
proposed in RALCK003.DOC by Andrew Milner including the support for
MBUNLOCK.NOW (supported by GoldEd 2.40+, RemoteAccess 2.00, FM 2.20).
* Before calling an external de-/compression utility, FastEcho checks
if the archive file is currently locked/opened by another task and
will skip it to prevent Share Violations when the utility tries to
access the file and doesn't have a proper exception handler.
* FastEcho was written in C++ (compiled with Borland C++ Version 3.1
(DOS), Borland C++ 4.02 with PowerPack (DPMI) and Borland C++ for
OS/2 2.0) and assembly language (Turbo Assembler Version 4.1).
FESetup was compiled with Watcom C++ 10.0a
───────────────────────────────────────────────────────────────────────
- 158 -
FastEcho MANUAL - A p p e n d i x e s -
───────────────────────────────────────────────────────────────────────
* File-IO is performed using standard DOS filehandle functions. The
PSP filehandle table is expanded to 230 entries.
* All programs automatically detect DESQview and write to its screen
buffer. They also furthermore detect Windows, OS/2 2.x as well as
PCMOS/386 and give up time-slices in these environments if possible
(when waiting for messagebase (un-)locking for example).
* The configuration file of FastEcho may be used with any newer GoldED
version using the "AREAFILE FastEcho <path>" keyword and with newer
timEd versions using the "FastEchoCFG <file+path>" keyword.
* The structures for 'C' and 'Pascal' of FastEcho.CFG are available as
FECFG146.RAR (or magic filename FECFG).
* The swapping routines used are provided by Thomas Wagner (EXEC 3.3)
and allow EMS-, XMS- and disk-swapping.
* FESetup makes intensive use of the TesSeRact CLX User Interface TCXL
Version 6.12 copyrighted by Innovative Data Concepts.
* The FESetup menu now sets the hard cursor to make its use easier for
blind people that use Braille terminals (SET FEOPT=SHOWCURSOR).
* FastEcho uses the JAM(mbp) API - Copyright 1993 Joaquim Homrighausen,
Andrew Milner, Mats Birch, Mats Wallin. ALL RIGHTS RESERVED.
About the OS/2 and the DPMI versions of FastEcho
================================================
Throughout this manual has already been pointed out all the exis-
ting differences between the DOS and DPMI versions (see chapter 13
through 13.5). The OS/2 characteristics are about the same of the DPMI
one. The DOS, DPMI and OS/2 release are dealt into three different ar-
chives:
FE146.RAR Contain the full DOS release with this documentation
FE146X.RAR Contain only the executables needed to run FastEcho
in protected mode
FE146P.RAR Contain only the executables needed to run FastEcho
in OS/2 native code.
You can reach these archives at your nearest FastEcho registration
site or Support Site.
───────────────────────────────────────────────────────────────────────
- 159 -
FastEcho MANUAL - A p p e n d i x e s -
───────────────────────────────────────────────────────────────────────
Help Systems, Registration Sites & Support
==========================================
If you want to register FastEcho or want to obtain nearer
information about FastEcho please refer to following Help systems:
Headquarters:
Software Technik Burchhardt
Mittelkamp 18
D-45731 Waltrop
Germany
Tel. ++49-2309-77597 (voice/answering machine)
++49-2309-77019 (data/fax/ISDN)
++49-2309-77499 (data)
++49-2309-91223 (ISDN)
Email: 2:2448/400@fidonet (Tobias Burchhardt)
9:492/6050@virnet
Internet: tobi@ttown.com
Help & Registration BeNeLux:
Slash - FastEcho Registrations
Postbus 502
5800 AM Venray
The Netherlands
Email: 2:512/5@fidonet (jeroen van de leur)
Internet: slash@xs4all.nl
Homepage: http://www.xs4all.nl/~slash/fastecho.html
Help & Registration Spain/Portugal:
Atlantis BBS
Apartado Postal 3.097
18080 Granada
Spain
Email: 2:345/801@fidonet (Alfredo Sanchez)
9:341/101@virnet
Help & Registration Austria:
HR-MailOrder! und mehr
c/o Herbert Riess jun.
Krieglergasse 2/19
A-1030 Wien
Austria
Email: 2:310/79@fidonet
───────────────────────────────────────────────────────────────────────
- 160 -
FastEcho MANUAL - A p p e n d i x e s -
───────────────────────────────────────────────────────────────────────
Help & Registration Canada:
Alex Stuart
2759 Belmont Ave.
Victoria, B.C.
Canada
V8R 4A9
Email: 1:340/30@fidonet
Registration United States of America and
International Credit Card orders:
FastEcho Registrations
Ed Meloan
1110 Terrace Circle Drive
North Augusta, SC 29841-4349
USA
Email: 1:360/1@fidonet
Internet: e.meloan@csra.net
Help & Registration Sweden:
Definite Solutions
Förskottsvägen 11
129 32 Hägersten
Sweden
Email: 2:201/329@fidonet (Mats Wallin)
Internet: mw@defsol.se
Help & Registration United Kingdom:
FastEcho Registrations UK
PO Box 443
Bangor
Co.Down, BT20 3BF
United Kingdom
Email: 2:443/13 (Colin Turner)
Help & Registration Italy:
FastEcho Reg.Site per l'Italia
Ugo Uggetti
Via Brigata Pavia, 8
27100 Pavia
Italy
Email: 2:331/501@fidonet
───────────────────────────────────────────────────────────────────────
- 161 -
FastEcho MANUAL - A p p e n d i x e s -
───────────────────────────────────────────────────────────────────────
Help & Registration Israel:
Rudy's Place BBS
PO BOX 8394
Rishon Le-Zion, 7525
Isreal
Email: 2:403/138@fidonet (Nemrod Kedem)
Help & Registration Australia/New Zealand:
Aquarius Communications
P.O. Box 4772
SYDNEY NSW 2001
Australia
Email: 3:714/930@fidonet (Glen Harvy)
Internet: registrations@aquarius.com.au
Homepage: http://www.aquarius.com.au
(Online registration possible)
Help & Registration Asia/Taiwan:
Aim Point BBS
Kuan-yu Chen
Check REGISTER.TWN for more details ...
Email: 6:720/255@fidonet
Help & Registration Ex-Soviet-Union States:
FastEcho Registrations
Egons Bush
20 Virzas street
Iecava, District Bauska
LV-1339 LATVIA
Email: 2:5100/8@fidonet
Help & Registration Poland
Integraal Microsystems
Biuro Handlowe
ul. Chmielna 12/4
00-020 Warszawa
Tel: ++48-22-276333 (voice)
++48-22-276333 (data from 9:00pm to
9:00am local time)
Email: 2:480/1496@fidonet (Andrzej Bursztynski)
76560.204@compuserve.com
For further information regarding registration, please refer to
the enclosed LICENSE.DOC and the registration forms in REGISTER.RAR!
───────────────────────────────────────────────────────────────────────
- 162 -
FastEcho MANUAL - A p p e n d i x e s -
───────────────────────────────────────────────────────────────────────
Support Sites
-------------
These sites always have the latest version of FastEcho available
for download or file-request, can provide help for setting up
FastEcho and will try to help when you have problems with FastEcho.
Alex Stuart Quantum Leap BBS 1:340/30 +1-604-595-4407
Mark Lewis Waldo's Place USA 1:3634/12 +1-919-774-5930
Mats Wallin Definite Solutions 2:201/329 +46-8-55630103
Jens Jensen FastEcho Support BBS 2:237/15 +45-63330011
Tobias Burchhardt WayForward BBS 2:2448/400 +49-2309-77019
jeroen van de leur Slash BBS 2:512/5 +31-478-550103
Herbert Riess Austria's MAIL Hupferl 2:310/79 +43-1-7101818
Ugo Uggetti Venus 2:331/501 +39-382-579979
Alfredo Sanchez Atlantis BBS 2:345/801 +34-58-132748
Nemrod Kedem Rudy's Place 2:403/138 +972-3-9667562
Andrzej Bursztynski Z-BBS [21:00-09:00] 2:480/1496 +48-22-6512544
Glen Harvy Aquarius 3:714/930 +61-2-9948-9122
Kuan-yu Chen FastEcho Support Asia 6:6/107 +886-2-255-0214
Official FTP site: ftp.ttown.com, pub/fastecho
FastEcho EchoMail & EchoFile Support
====================================
Watch out for the international FidoNet help conference FE_HELP
which is currently available on the U.S. backbone and at least in Zone
2. If you have problems to get this area contact Tobias Burchhardt
or one of your nearest support sites. For german-speaking FidoNet
members the help conference FASTECHO.GER is available in Regions 24,
30 and 31. For users in Region 28 please refer to FASTECHO.028. For
Italian-speaking Fidonet members the help conference FASTECHO.ITA is
available. All FastEcho public releases and FastEcho related utilities
are hatched into a echofile named FastEcho, for details on that topic
please contact your nearest support site or betatester. If you need
always the last FastEcho release, utilities and tools for FastEcho then
ask for the official FastEcho FileEcho area which is mainly available
on the Z1 filebone and several other places too. Ask your nearest
support site or beta site for its availability.
Thanks
I would like to thank all the people who contributed, with their
ideas and suggestions, to the creation of this manual. Very special
thanks to Tobias and to all the irreplaceable beta crew, expecially to
Raymond Dijkxhoorn who collected all the possible FastEcho FAQ. Thanks,
also, to all the FastEcho guys in FE_HELP.331 and POINT.ITA for sugges-
ting some additional subject they wished to be dealt herein.
To contact me refer to the following addresses:
2:2448/400.7@Fidonet.org
2:331/501.25@Fidonet.org
2:332/300.100@Fidonet.org
.-.-.
..And I never forgotten gipsy girl and what she said to me..
───────────────────────────────────────────────────────────────────────
- 163 -
FastEcho MANUAL - Smart Index -
───────────────────────────────────────────────────────────────────────
┌─────────────────────────────────┐
│ S M A R T I N D E X │
└─────────────────────────────────┘
- A -
16 bit dpmi version vs. dos version................................ 150
4D/type 2+ (Node configuration).................................... 51
Active column (forward requests)................................... 103
Add '+' (forward areafix requests)................................. 107
Add '+'............................................................ 57
Add '---' (forward areafix requests)............................... 107
Add '---' <tearline>............................................... 57
Add list to receipts (areafix options)............................. 100
Add node (global changes) (area manager)........................... 83
Addressing type (4d/type 2+ node configuration).................... 51
Advanced Options................................................... 24
After unpack (external programs)................................... 41
Aka (your aka in node configuration)............................... 46
Allow %compress (areafix options).................................. 99
Allow %FROM........................................................ 55
Allow %PKTPWD (AreaFix Options).................................... 99
Allow %PWD (AreaFix Options)....................................... 99
Allow %RESCAN (AreaFix Options).................................... 98
Allow area deletion................................................ 56
Allow area renaming................................................ 56
Allow Rescan....................................................... 55
Appendix (A) - Zone/Net/Node/Point................................. 152
Appendix (B) - Message Kludges..................................... 153
Appendix (C) - Message Attributes.................................. 155
Appendix (D) - Technical notes..................................... 157
Archive extensions (Inbound)....................................... 32
Archive extensions (Outbound)...................................... 32
ARCmail (node configuration)....................................... 46
ARCmail attaches (Kill)............................................ 33
ARCmail attaches status (node configuration)....................... 47
ARCmail Options.................................................... 31
ARCmail sizing..................................................... 23
ARCmail type 0.60.................................................. 51
Area Configuration................................................. 68
Area definition layout............................................. 69
Area list (forward areafix requests)............................... 104
Area-Create (Allow)................................................ 52
AreaFix (linking one or more new areas)............................ 89
AreaFix (Options).................................................. 97
AreaFix (Password)................................................. 47
AreaFix (unlinking one or more areas).............................. 90
AreaFix (What is).................................................. 89
AreaFix (Wilcarded Link/Unlink).................................... 90
AreaFix flags...................................................... 54
AreaFix logfile name and path definition........................... 20
AreaFix MetaCommand %AVAIL......................................... 92
AreaFix Metacommand %COMPRESS <type> <?>........................... 94
AreaFix MetaCommand %DAYS <nnn>.................................... 93
AreaFix MetaCommand %EXPORT........................................ 96
───────────────────────────────────────────────────────────────────────
- 164 -
FastEcho MANUAL - Smart Index -
───────────────────────────────────────────────────────────────────────
AreaFix Metacommand %FROM <net address>............................ 95
AreaFix MetaCommand %HELP.......................................... 95
AreaFix MetaCommand %INFO.......................................... 91
AreaFix MetaCommand %LIST.......................................... 91
AreaFix MetaCommand %MSGS <nnn>.................................... 93
AreaFix MetaCommand %NOEXPORT...................................... 96
AreaFix MetaCommand %NOTE.......................................... 92
AreaFix MetaCommand %PAUSE......................................... 92
AreaFix Metacommand %PKTPWD <password>............................. 95
AreaFix Metacommand %PWD <password>................................ 94
AreaFix MetaCommand %QUERY......................................... 91
AreaFix MetaCommand %QUIT.......................................... 96
AreaFix MetaCommand %RESCAN........................................ 92
AreaFix MetaCommand %RESUME........................................ 92
AreaFix MetaCommand %UNLINKED...................................... 91
AreaFix MetaCommands............................................... 89
AreaFix Options (add list to receipts)............................. 100
AreaFix Options (allow %compress).................................. 99
AreaFix Options (Allow %PKTPWD).................................... 99
AreaFix Options (Allow %PWD)....................................... 99
AreaFix Options (Allow %RESCAN).................................... 98
AreaFix Options (default for rescan)............................... 98
AreaFix Options (defaults for %days)............................... 99
AreaFix Options (defaults for %msgs)............................... 98
AreaFix Options (Detailed List).................................... 100
AreaFix Options (file for %help definition)........................ 102
AreaFix Options (forward requests)................................. 102
AreaFix Options (Keep receipts).................................... 100
AreaFix Options (Keep requests).................................... 100
AreaFix Options (max. receipt size)................................ 102
AreaFix Options (maximum for %days)................................ 99
AreaFix Options (maximum for %msgs)................................ 99
AreaFix Options (password in %info)................................ 101
AreaFix Options (rescan defaults).................................. 98
AreaFix Options (rulefile area tag prefix)......................... 101
AreaFix Options (scan before tossing).............................. 100
AreaFix Options (send conference rules)............................ 101
AreaFix receipts status (node configuration)....................... 48
AreaFix type....................................................... 56
AREAS.BBS (Export)................................................. 109
ASCII file (Export)................................................ 109
Attributes (Message)............................................... 155
Auto Area Create................................................... 26
Automatic error report............................................. 144
Automatic inclusion of user.bbs file............................... 36
Automatic passive (node configuration)............................. 58
Autorenumber....................................................... 35
AVAIL (AreaFix MetaCommand)........................................ 92
Average ratio definition in compression programs................... 38
───────────────────────────────────────────────────────────────────────
- 165 -
FastEcho MANUAL - Smart Index -
───────────────────────────────────────────────────────────────────────
- B -
Batch files example................................................ 148
BBS configuration (auto updating).................................. 26
BBS Configuration location......................................... 19
BBS defaults for the new areas (auto updating)..................... 27
BBS Software definition............................................ 13
Be 'quiet'......................................................... 14
Before Pack (External programs).................................... 41
Binkeley style NetMail packing..................................... 123
Board (Area Configuration)......................................... 73
Board (default).................................................... 65
Buffer for the Toss operation...................................... 30
- C -
Calling conventions................................................ 40
Carbon Copies (Copy to)............................................ 87
Carbon Copies (Examples)........................................... 88
Carbon copies (search for string).................................. 87
Carbon copies (suggestions and notes).............................. 88
Carbon Copies (Test)............................................... 86
Carbon Copies...................................................... 86
Check complete Inbound files....................................... 33
Check mailer semaphores............................................ 32
Command line switches (FESetup).................................... 8
Comment (Area Configuration)....................................... 70
Comment (default).................................................. 63
Compatibility problems using the included dpmi server.............. 150
COMPRESS (AreaFix MetaCommand)..................................... 94
Compress mail after................................................ 24
Compress mail free................................................. 24
Compression Programs............................................... 37
Compression ratio (Maximum)........................................ 33
Configuration of nodes............................................. 45
Convert umlaut (area configuration)................................ 75
Convert Umlaut..................................................... 52
Copy to (Carbon Copies)............................................ 87
Cpd circular path detection (area configuration)................... 74
Create "in session" (mailer's semaphores).......................... 32
Create as passtrough (forward areafix requests).................... 108
- D -
Data DropDown Menu................................................. 44
DAYS (AreaFix MetaCommand)......................................... 93
Days purging (area configuration).................................. 77
DB Environment variable............................................ 139
Decompression Programs............................................. 39
Default Aka........................................................ 66
Default board...................................................... 65
Default comment.................................................... 63
Default Export-To.................................................. 67
Default for rescan (areafix options)............................... 98
Default origin..................................................... 63
───────────────────────────────────────────────────────────────────────
- 166 -
FastEcho MANUAL - Smart Index -
───────────────────────────────────────────────────────────────────────
Default path....................................................... 65
Default SEEN-BY.................................................... 66
Default storage.................................................... 65
Default type....................................................... 64
Defaults for %days (areafix options)............................... 99
Defaults for %msgs (areafix options)............................... 98
Defaults for area groups (set-up).................................. 62
Defaults for the areas automatically created....................... 52
Defaults for the areas automatically created....................... 54
Del Key - Delete (Node Manager).................................... 62
Delete node (global changes) (area manager)........................ 84
Deleting areas via AreaFix......................................... 96
Deny list (forward areafix requests)............................... 106
Description........................................................ 3
Destination of PKTs (check)........................................ 29
Detailed List (AreaFix Options).................................... 100
Differences between dos and 16 bit dpmi versions................... 150
Differences between the dos and protected mode versions............ 151
DIRECT (Routing)................................................... 120
Disable passive (area configuration)............................... 76
DPMI and dos mode version differences.............................. 159
DPMI Runtime module options........................................ 159
DPMI server compatibility problems................................. 150
DPMI version (precautions using)................................... 150
DPMI version of FastEcho........................................... 163
DPMI Version Requirements.......................................... 150
DPMI version....................................................... 150
Duperecords (limits and enabling).................................. 22
Duplicates (automatic kill of)..................................... 28
- E -
Echolist (Export).................................................. 109
EchoMail (What is)................................................. 42
EchoMail vs. NetMail (matrix)...................................... 42
EchoMail/EchoFile Support.......................................... 163
EMS (use for buffering)............................................ 29
Enter Key - Edit (Area Manager).................................... 80
Enter Key - Edit (Node Manager).................................... 59
Environment variables (FD,IM,DB)................................... 139
Environment variables (FE)......................................... 140
Environment variables (FEMAXMEM)................................... 141
Environment variables (FEOPT)...................................... 141
Environment variables (FEUTMP)..................................... 140
Environment variables (HMBLOCK).................................... 140
Environment variables (TZUTC)...................................... 140
ENVIRONMENT VARIABLES.............................................. 139
Error reporting (Automatic)........................................ 144
Errorlevels........................................................ 145
Examples (Carbon Copies)........................................... 88
Examples (Direct Routing).......................................... 118
Examples (FEUtil Post)............................................. 136
Examples (ROUTE.FE)................................................ 122
Examples (Security)................................................ 78
EXCEPT (Routing)................................................... 120
───────────────────────────────────────────────────────────────────────
- 167 -
FastEcho MANUAL - Smart Index -
───────────────────────────────────────────────────────────────────────
Exclude SysOps..................................................... 36
Exclude Users...................................................... 35
EXPORT (AreaFix MetaCommand)....................................... 96
Export AREAS.BBS................................................... 109
Export ASCII file.................................................. 109
Export by name..................................................... 54
Export DropDown Menu............................................... 109
Export Echolist.................................................... 109
Export ROUTE.FE.................................................... 110
Export SQUISH.CFG.................................................. 109
Export-to (Area Configuration)..................................... 79
Export-To (default)................................................ 67
Extensions of Inbound archives..................................... 32
Extensions of Outbound archives.................................... 32
External programs (after unpack)................................... 41
External programs (Before Pack).................................... 41
External programs.................................................. 40
- F -
F2 Key - Routing (Node Manager).................................... 59
F2 Key - Sorting (Area Manager).................................... 81
F3 Key - Browse (Node Manager)..................................... 60
F3 Key - Tag (Area Manager)........................................ 81
F3 key - tag by group (area manager)............................... 82
F3 key - tag by name (area manager)................................ 81
F4 key - area list (node manager).................................. 61
F4 Key - Search (Area Manager)..................................... 82
F5 Key - Copy (Area Manager)....................................... 82
F5 Key - Copy (Node Manager)....................................... 61
F6 key 'global' (add node) (area manager).......................... 83
F6 key 'global' (delete node) (area manager)....................... 84
F6 key 'global' (other items) (area manager)....................... 85
F6 key 'global' (replace <node> with <node>) (area manager)........ 85
F6 Key - Global (Area Manager)..................................... 83
FastEcho Afix...................................................... 124
FastEcho EchoMail & EchoFile support............................... 163
FastEcho F.A.Q..................................................... 157
FastEcho Help...................................................... 125
FastEcho Notify.................................................... 124
FastEcho Pack (in general)......................................... 117
FastEcho Pack -F................................................... 123
FastEcho Pack -I................................................... 123
FastEcho Pack -P................................................... 123
FastEcho pack -r<route filename>................................... 119
FastEcho pack <addr> <addr> <...> via <addr>....................... 117
FastEcho Relink.................................................... 125
FastEcho Scan (in general)......................................... 114
FastEcho Scan -A................................................... 115
FastEcho Scan -F................................................... 116
FastEcho Scan -I................................................... 116
FastEcho Scan -L<file>............................................. 116
FastEcho Scan -N................................................... 115
FastEcho Stat (in general)......................................... 126
FastEcho Stat -G<groups>........................................... 126
FastEcho Stat -H................................................... 127
───────────────────────────────────────────────────────────────────────
- 168 -
FastEcho MANUAL - Smart Index -
───────────────────────────────────────────────────────────────────────
FastEcho Stat -N................................................... 127
FastEcho Stat -O................................................... 127
FastEcho Stat -R................................................... 126
FastEcho Stat -RS.................................................. 126
FastEcho Toss (in general)......................................... 112
FastEcho Toss -B................................................... 113
FastEcho Toss -C................................................... 113
FastEcho Toss -F................................................... 114
FastEcho Toss -S................................................... 114
FD Environment variable............................................ 139
FE environment variable............................................ 140
FEMAXMEM environment variable...................................... 141
FEOPT environment variable......................................... 141
FESetup TopBar Dropdown menu....................................... 7
FESetup, dos command line switches................................. 8
FEUtil Check -D[elete]............................................. 133
FEUtil Check....................................................... 133
FEUtil Import (in general)......................................... 137
FEUtil Import -Excl<file>.......................................... 138
FEUtil Import -FORCE............................................... 138
FEUtil Import -Incl<file>.......................................... 138
FEUtil Index....................................................... 128
FEUtil Link (in general)........................................... 129
FEUtil Link -F[orce]............................................... 130
FEUtil Link -I[gnore].............................................. 130
FEUtil Move........................................................ 134
FEUtil Pack (in general)........................................... 131
FEUtil Pack -D[elete].............................................. 132
FEUtil Pack -F[orce]............................................... 131
FEUtil Pack -O[verwrite]........................................... 132
FEUtil Pack -Q[uick]............................................... 132
FEUtil Pack -R[enumber]............................................ 132
FEUtil parameters.................................................. 34
FEUtil post examples & application................................. 136
FEUtil Post........................................................ 134
FEUtil Purge (in general).......................................... 130
FEUtil Purge -D[elete]............................................. 131
FEUtil Sort (in general)........................................... 132
FEUtil Sort -B[ackup].............................................. 133
FEUtil Undelete.................................................... 133
FEUTMP environment variable........................................ 140
File for %help definition (areafix options)........................ 102
Filenames definition............................................... 20
Files created or used by fastecho.................................. 147
Flags (NO386)...................................................... 141
Flags (NOAFIX)..................................................... 142
Flags (NOAUTOFAIL)................................................. 143
Flags (NODUPES).................................................... 142
Flags (NOEMS,NOXMS)................................................ 142
Flags (NOERREP).................................................... 144
Flags (NOEXPORT)................................................... 142
Flags (NOLIMIT).................................................... 143
Flags (NOMSGID).................................................... 143
Flags (NOPACK)..................................................... 142
Flags (NORES)...................................................... 144
Flags (NOSEENBY)................................................... 142
Flags (PACKONE).................................................... 143
───────────────────────────────────────────────────────────────────────
- 169 -
FastEcho MANUAL - Smart Index -
───────────────────────────────────────────────────────────────────────
Flags (RDEBUG)..................................................... 143
Flags (SHOWCURSOR)................................................. 143
Flags (STRIPTEAR).................................................. 143
Flags (USEBIOS).................................................... 141
Flags (ZONEGATE)................................................... 144
Force Mailer Rescan................................................ 28
Foreword........................................................... 1
Forward (forward areafix requests)................................. 104
Forward AreaFix requests (add '+')................................. 107
Forward AreaFix requests (add '---')............................... 107
Forward AreaFix requests (area list)............................... 104
Forward AreaFix requests (create as passthrough)................... 108
Forward AreaFix requests (deny list)............................... 106
Forward AreaFix requests (forward)................................. 104
Forward AreaFix requests (groups).................................. 106
Forward AreaFix requests (list type)............................... 105
Forward AreaFix requests (new area default group).................. 107
Forward AreaFix requests (remote program).......................... 105
Forward AreaFix requests (security)................................ 107
Forward AreaFix requests (setup)................................... 103
Forward AreaFix requests (unconditional)........................... 104
Forward changes.................................................... 57
Forward requests (active column)................................... 103
Forward requests (areafix options)................................. 102
Forward requests (Forward to)...................................... 103
Forward requests (List file)....................................... 103
Forward requests (remote program column)........................... 103
Forward requests................................................... 55
FORWARD-FOR (Routing).............................................. 121
FORWARD-TO (Routing)............................................... 120
Frequently Asked Questions......................................... 157
FROM (AreaFix MetaCommand)......................................... 95
Function keys active in 'area manager'............................. 80
Function Keys in 'Node Manager'.................................... 58
- G -
Global (add node) (area manager)................................... 83
Global (delete node) (area manager)................................ 84
Global (replace <node> with <node>) (area manager)................. 85
Global (the other global items) (area manager)..................... 85
Graphical tossing.................................................. 30
Group (Area Configuration)......................................... 70
Group area defaults (other switches)............................... 66
Group Area Defaults (set-up)....................................... 62
Group names........................................................ 41
Groups (forward areafix requests).................................. 106
Groups available (node configuration).............................. 50
Grunged date (killing)............................................. 36
───────────────────────────────────────────────────────────────────────
- 170 -
FastEcho MANUAL - Smart Index -
───────────────────────────────────────────────────────────────────────
- H -
HELP (AreaFix MetaCommand)......................................... 95
Help on line....................................................... 111
Help Systems, Registration Sites & Support......................... 160
Hide Area (Area Configuration)..................................... 77
HMB directory definition........................................... 16
HMB Sharing........................................................ 28
HMBLOCK environment variable....................................... 140
- I -
Ignore old semaphores.............................................. 24
IM Environment variable............................................ 139
Import DropDown Menu............................................... 110
Inbound archives extensions........................................ 32
Inbound directory definition....................................... 16
Inbound files (check if complete).................................. 33
Include USERS.BBS.................................................. 36
INFO (AreaFix MetaCommand)......................................... 91
Infozip calling conventions........................................ 40
Ins key - new entry (node manager)................................. 61
Ins/del keys - global (area manager)............................... 85
- K -
Keep netmails (area configuration)................................. 77
Keep NetMails...................................................... 36
Keep receipts (AreaFix Options).................................... 100
Keep requests (AreaFix Options).................................... 100
Keep seen-by (area configuration).................................. 74
Keep tearline clean................................................ 25
Keep Users (Area Configuration).................................... 76
Kill duplicates.................................................... 28
Kill empty NetMails................................................ 27
Kill grunged date.................................................. 36
Kill Read (Area Configuration)..................................... 76
Kill stray attaches................................................ 33
Kludges (message).................................................. 153
- L -
Linking one or more new areas (areafix)............................ 89
LIST (AreaFix MetaCommand)......................................... 91
List file (Forward Requests)....................................... 103
List type (forward areafix requests)............................... 105
LISTED (Route Macro)............................................... 122
Local inbound directory definition................................. 17
Logfile directory/name definition.................................. 20
Logging............................................................ 30
───────────────────────────────────────────────────────────────────────
- 171 -
FastEcho MANUAL - Smart Index -
───────────────────────────────────────────────────────────────────────
- M -
Macro in Route file................................................ 121
Mailer configuration (auto updating)............................... 26
Mailer Rescan (Forced)............................................. 28
Mailer type definition............................................. 13
Mailer's semaphores (check)........................................ 32
Mailer's semaphores (create "in session").......................... 32
Main address (node configuration).................................. 46
Mandatory (Area Configuration)..................................... 74
Max. receipt size (areafix options)................................ 102
Maximum ARCmail size............................................... 23
Maximum compression ratio.......................................... 33
Maximum for %days (areafix options)................................ 99
Maximum for %msgs (areafix options)................................ 99
Maximum Messages per PKT........................................... 23
Maximum open .QQQs................................................. 22
Maximum Pkt size................................................... 23
Maximum size of the archives produced by packers................... 49
Maximum size....................................................... 49
Message Attributes................................................. 155
Message buffer size................................................ 22
Message kludges.................................................... 153
Message purging (area configuration)............................... 77
Messagebase directory definition (hmb)............................. 16
Minimal System Requirements........................................ 4
Minimum Inbound .PKTs size......................................... 23
Miscellaneous (System)............................................. 13
MSGS (AreaFix MetaCommand)......................................... 93
MYNET (Route macro)................................................ 121
MYPOINTS (Route macro)............................................. 122
MYZONE (Route macro)............................................... 121
- N -
Name (Area Configuration).......................................... 69
Name (Node configuration).......................................... 46
Net explanation.................................................... 152
Netmail (automatic kill of empty).................................. 27
NetMail (What is).................................................. 43
Netmail directory definition (primary)............................. 15
NetMails (keep).................................................... 36
Network addresses.................................................. 11
New area default group (forward areafix requests).................. 107
New area default group............................................. 54
New area defaults.................................................. 27
NO-ROUTE (Routing)................................................. 120
NO386 flag......................................................... 141
NOAFIX flag........................................................ 142
NOAUTOFAIL flag.................................................... 143
Node Configuration................................................. 45
Node explanation................................................... 152
Nodes security (node configuration)................................ 50
NODUPES flag....................................................... 142
NOEMS flag......................................................... 142
NOERREP flag....................................................... 144
───────────────────────────────────────────────────────────────────────
- 172 -
FastEcho MANUAL - Smart Index -
───────────────────────────────────────────────────────────────────────
NOEXPORT (areafix metacommand)..................................... 96
NOEXPORT flag...................................................... 142
NOLIMIT flag....................................................... 143
NOMSGID flag....................................................... 143
NOPACK flag........................................................ 142
NORES flag......................................................... 144
NOSEENBY flag...................................................... 142
NOTE (AreaFix MetaCommand)......................................... 92
Notes about FEUtil................................................. 139
NOXMS flag......................................................... 142
- O -
Obtaining better performance....................................... 5
Optimized i386 routines............................................ 5
Options (ARCmail).................................................. 31
Options (AreaFix).................................................. 97
Origin (Area Configuration)........................................ 71
Origin (default)................................................... 63
Origins (Definition)............................................... 42
OS/2 version of FastEcho........................................... 163
Out-of-zone echomail message....................................... 144
Outbound archive extensions........................................ 32
Outbound directory definition...................................... 17
Outbound Type (Temporary).......................................... 31
- P -
Pack priority...................................................... 52
Packer maximum size................................................ 49
Packer selection (node configuration).............................. 49
Packet - Password.................................................. 47
PACKONE flag....................................................... 143
Parameters (System)................................................ 21
Passive (Area Configuration)....................................... 75
Passive (automatic switching to)................................... 58
Passive (Node configuration)....................................... 58
Password in %info (areafix options)................................ 101
Passwords (areafix - node configuration)........................... 47
Passwords (Node configuration)..................................... 47
Passwords (packet - node configuration)............................ 47
Passwords.......................................................... 47
Path (Area Configuration).......................................... 73
Path (default)..................................................... 65
Pathnames.......................................................... 15
PAUSE (AreaFix MetaCommand)........................................ 92
PKTPWD (AreaFix MetaCommand)....................................... 95
Pkts (maximum number of messages contained)........................ 23
PKTs destination (check)........................................... 29
Point explanation.................................................. 152
Precautions using the dpmi version................................. 150
───────────────────────────────────────────────────────────────────────
- 173 -
FastEcho MANUAL - Smart Index -
───────────────────────────────────────────────────────────────────────
Preliminary Operations............................................. 6
PURGE - Days....................................................... 35
PURGE - Messages................................................... 34
PURGE - Rcvd Days.................................................. 35
PURGE defaults..................................................... 34
Purging (Area Configuration)....................................... 77
Purging (days) (area configuration)................................ 77
Purging (msgs) (area configuration)................................ 77
Purging (rcvd days) (area configuration)........................... 77
PWD (AreaFix MetaCommand).......................................... 94
- Q -
QQQs files (maximum handles)....................................... 22
- R -
RDEBUG flag........................................................ 143
Read (security) (area configuration)............................... 78
Received days purging (area confgiguration)........................ 77
Registrations...................................................... 1
Relink (FastEcho commandline)...................................... 125
Remote changes (area configuration)................................ 76
Remote program (forward areafix requests).......................... 105
Remote program column (forward requests)........................... 103
Remote program..................................................... 56
Renaming areas via AreaFix......................................... 96
Replace <node> with <node> (area manager).......................... 85
Requirements of the fastecho dpmi version.......................... 150
RESCAN (AreaFix MetaCommand)....................................... 92
Rescan (Mailer).................................................... 28
Rescan defaults (areafix options).................................. 98
RESCAN special syntax.............................................. 96
Respond to RRQ..................................................... 29
RESUME (AreaFix MetaCommand)....................................... 92
Retear............................................................. 25
Return receipt request (automatic answering)....................... 29
Route Macro (LISTED)............................................... 122
Route Macro (MYNET)................................................ 121
Route Macro (MYPOINTS)............................................. 122
Route Macro (MYZONE)............................................... 121
ROUTE-TO (Routing)................................................. 119
ROUTE.FE (examples)................................................ 122
ROUTE.FE (Export).................................................. 110
Routing 'ROUTE-TO'................................................. 119
Routing (commandline) statements................................... 117
Routing (DIRECT)................................................... 120
Routing (EXCEPT)................................................... 120
Routing (file) statements (route.fe)............................... 119
Routing (FORWARD-FOR).............................................. 121
Routing (FORWARD-TO)............................................... 120
Routing (NO-ROUTE)................................................. 120
Routing address' macro............................................. 121
Routing Direct (Examples).......................................... 118
Routing shortcuts (shortened points routing)....................... 117
───────────────────────────────────────────────────────────────────────
- 174 -
FastEcho MANUAL - Smart Index -
───────────────────────────────────────────────────────────────────────
Routing shortcuts (wilcards/abbreviations/macros).................. 117
RRQ (Automatic answering).......................................... 29
Rt. values in compression programs................................. 38
Rule files directory definition.................................... 19
Rulefile area tag prefix (areafix options)......................... 101
Rules (Send) ...................................................... 55
- S -
Scan before tossing (areafix options).............................. 100
Search for string (carbon copies).................................. 87
Security (Examples)................................................ 78
Security (forward areafix requests)................................ 107
Security (Node configuration)...................................... 50
Security (read) (area configuration)............................... 78
Security (write) (area configuration).............................. 78
Security settings in area configuration............................ 78
Security........................................................... 29
SEEN-BY (Area Configuration)....................................... 79
SEEN-BY (default).................................................. 66
Seen-by for out-of-zone echomail messages.......................... 144
Semaphore files.................................................... 145
Semaphores (check mailers)......................................... 32
Semaphores (mailer - create "in session").......................... 32
Semaphores directory definition.................................... 18
Send conference rules (areafix options)............................ 101
Send Help (Node configuration)..................................... 58
Send notify (node configuration)................................... 57
Send Rules......................................................... 55
Setting for outbound arcmail bundles size.......................... 23
Setup (forward areafix requests)................................... 103
Share HMB.......................................................... 28
Shareware Notice................................................... 1
Sharing the messagebase............................................ 5
SHOWCURSOR flag.................................................... 143
Size of message buffer (maximum)................................... 22
Size of outbound arcmail bundles................................... 23
Size of Pkts (maximum)............................................. 23
Size of Pkts (minimum)............................................. 23
Special %RESCAN syntax............................................. 96
Special AreaFix MetaCommands....................................... 96
SQUISH.CFG (Export)................................................ 109
Static queue....................................................... 19
Statistic file name and path definition............................ 21
Status (ARCmail)................................................... 47
Status (AreaFix)................................................... 48
Status............................................................. 47
Storage (default).................................................. 65
Storage type (area configuration).................................. 72
Strip any tearline................................................. 25
STRIPTEAR flag..................................................... 143
Suggestions (General).............................................. 5
Suggestions and notes (carbon copies).............................. 88
Swapping directory definition...................................... 19
Swapping........................................................... 14
SysOps exclusion................................................... 36
SYSTEM TopBar Dropdown menu........................................ 11
───────────────────────────────────────────────────────────────────────
- 175 -
FastEcho MANUAL - Smart Index -
───────────────────────────────────────────────────────────────────────
- T -
Tag by Group (Area Manager)........................................ 82
Tag by name........................................................ 81
Tearline stripping................................................. 25
Tearline........................................................... 26
Technical notes.................................................... 161
Temporary inbound directory definition............................. 16
Temporary outbound directory definition............................ 18
Temporary Outbound Type............................................ 31
Test (Carbon Copies)............................................... 86
Thanks............................................................. 164
The FESetup Main Menu.............................................. 6
Tiny seen-by (area configuration).................................. 74
Toss Buffer........................................................ 30
TosScan............................................................ 51
Tutorial........................................................... 5
Type (Area Configuration).......................................... 71
Type (default)..................................................... 64
TZUTC environment variable......................................... 140
- U -
Umlaut conversion (area configuration)............................. 75
Umlaut conversion.................................................. 52
Unconditional (forward areafix requests)........................... 104
UNLINKED (AreaFix MetaCommand)..................................... 91
Unlinking one or more areas (areafix).............................. 90
Unpack Unprotected................................................. 33
Unprotected inbound (allow unpacking).............................. 33
Unprotected inbound directory definition........................... 16
Update BBS config.................................................. 26
Update Mailer Configuration........................................ 26
Use Aka (Area Configuration)....................................... 73
Use Aka (default).................................................. 66
Use arrival date................................................... 35
Use EMS for buffering.............................................. 29
USEBIOS flag....................................................... 141
User names......................................................... 12
Users exclusion.................................................... 35
Using FastEcho..................................................... 111
Using FEUtil....................................................... 127
- W -
What FastEcho does................................................. 2
What's AreaFix..................................................... 89
Wilcarded Link/Unlink (AreaFix).................................... 90
Wilcards (using them in routing)................................... 117
Write (security) (area configuration).............................. 78
- Y -
Your AKA........................................................... 46
- Z -
Zone/Net/Node/Point explanation.................................... 152
ZONEGATE flag...................................................... 144
───────────────────────────────────────────────────────────────────────
- 176 -